locked
IVsPersistHierarchyItem2.ReloadItem() throws System.AccessViolationException on Visual Studio 2017 RRS feed

  • Question

  • Hi,

    In my VSIP application, IVsPersistHierarchyItem2.ReloadItem() throws System.AccessViolationException on Visual Studio 2017 when the project is created from the Windows Desktop Application of VC++ template.  Same is working fine with Visual Studio 2015 & 2013.

    Can any one guess or explain the reason for the same?

    Below is the stack trace

    Microsoft.VisualStudio.Shell.Interop.IVsSolution.GetItemOfProjref(String pszProjref, IVsHierarchy& ppHierarchy, UInt32& pitemid, String& pbstrUpdatedProjref, VSUPDATEPROJREFREASON[] puprUpdateReason)\r\n   
     at Microsoft.VisualStudio.Platform.WindowManagement.SolutionOptions.ReopenDocumentFrame(WindowManagerService windowManager, StubWindowInfo stubInfo, ReopenDocumentOptions options, DocumentGroup docGroup, Int32& hr)\r\n   
     at Microsoft.VisualStudio.Platform.WindowManagement.SolutionOptions.ReopenDocumentFrame(IWindowManagerPrivate windowManager, StubWindowInfo stubInfo, ReopenDocumentOptions options, DocumentGroup docGroup, Int32& hr)\r\n   
     at Microsoft.VisualStudio.Platform.WindowManagement.SolutionOptions.ReopenDocumentFrame(IWindowManagerPrivate windowManager, StubWindowInfo stubInfo, ReopenDocumentOptions options, DocumentGroup docGroup)\r\n   
     at Microsoft.VisualStudio.Platform.WindowManagement.SolutionOptions.<>c__DisplayClass22_0.<LoadBinaryDocumentStates>b__0(VersionedBinaryReader VersionedBinaryReader)\r\n   
     at Microsoft.VisualStudio.Utilities.VersionedBinaryReader.ReadVersioned(Int32 expectedVersion, ReadCallback callback, Boolean throwOnUnexpectedVersion)\r\n   
     at Microsoft.VisualStudio.Platform.WindowManagement.SolutionOptions.LoadBinaryDocumentStates(WindowManagerService windowManager, IStream comStream, Boolean isExternal)\r\n   
     at Microsoft.VisualStudio.Platform.WindowManagement.SolutionOptions.LoadDocumentStates(WindowManagerService windowManager, IStream comStream, Boolean isExternal)\r\n   
     at Microsoft.VisualStudio.Platform.WindowManagement.WindowManagerService.<>c__DisplayClass174_0.<LoadDocumentStates>b__0()\r\n   
     at Microsoft.VisualStudio.ErrorHandler.CallWithCOMConvention(Action method, Boolean reportError)\r\n   
     at Microsoft.VisualStudio.Platform.WindowManagement.WindowManagerService.LoadDocumentStates(IStream stream, Int32 fExternal)\r\n   
     at Microsoft.VisualStudio.Shell.Interop.IVsPersistHierarchyItem2.ReloadItem(UInt32 itemid, UInt32 dwReserved)\r\n   ......

    Thanks in Advance

    Paramesh

    Friday, August 25, 2017 3:36 PM

All replies

  • Hi Paramesh A,

    Thank you for posting here.

    According to your question is more related to VSIP, I will move it to Visual Studio Integrate forum for suitable support.

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions.

    Best Regards,

    Wendy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Monday, August 28, 2017 8:00 AM
  • Hi Paramesh,

    Since works fine in previous version of Visual Studio, please check your Visual Studio 2017 to make sure it is in the latest version. You could check Visual Studio update from Tools -> Extensions and Updates -> Updates -> Product Updates in Visual Studio 2017 menu.

    If your Visual Studio 2017 is the latest version, please create a new VSIP application to check whether only this specific project has this issue or all projects have this issue. If all projects have this issue, there should be some problem on Visual Studio 2017 itself. Please repair your Visual Studio 2017.

    If just this specific project has this issue, please share some code snippet and the detailed steps about how do you create VSIP application in Visual Studio 2017 to help us reproduce this problem.

    Best Regards,
    Weiwei


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, August 29, 2017 2:59 AM