2
Not properly documenting for VS2026
Problem reported by Rick Mathers - 11/12/2025 at 8:18 AM
Being Fixed
After upgrading VS to VS2026 I noticed that it does not document the file as expected.  See below for portion of the log file showing an exception.  I can confirm that the namespace documents as well as the header is partially documented, but drops the assembly name, but classes, records, properties, etc fail to document.

Date and Time: 11/12/2025 10:06:58 AM
IP Address: {0}
OS Platform: Win32NT
Processor: AMD64
OS version: 10.0.26100.0
Current user role:  User;

Allocated Memory: 751 Mb
Available Physical Memory: 1 Mb
Available Virtual Memory: 1 Mb
Total Physical Memory: 3769 Mb
Total Virtual Memory: 697 Mb
Percentage of physical memory In use: 42 %

NET Framework version: 4.0.30319.42000
Visual Studio version: 18.0
Visual Studio file: C:\Program Files\Microsoft Visual Studio\18\Professional\Common7\IDE\devenv.exe
Visual Studio file version: 18.0.11205.157

Application Domain: DefaultDomain
Product Version: 
Assembly Codebase: file:///c:/users/{REDACTED}/appdata/local/microsoft/visualstudio/18.0_8b93e5a5/extensions/2nm2xrjh.quw/SubMain.GhostDoc.Core.DLL
Assembly Version: 2.2.0.0
Assembly Build Date: 11/12/2025 9:36:02 AM
Assembly Full Name: SubMain.GhostDoc.Core, Version=2.2.0.0, Culture=neutral, PublicKeyToken=94c677ee32cc1929

Exception Source: Microsoft.VisualStudio.Interop
Exception Type: System.Runtime.InteropServices.COMException
Exception Message: DocumentMember: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
Exception Target Site: get_Parent

---- Stack Trace ----
 EnvDTE.CodeProperty.get_Parent()
 SubMain.GhostDoc.Core.DLL: N 00000
 A.c4beb3839d623f2af95010cd0951cf1bb.c0012a3cfd6f80130a0508007ae497b4b( As Object)
 SubMain.GhostDoc.Core.DLL: N 00030
 SubMain.GhostDoc.T4.CodeElement..ctor(ctxtObj As Object, codeElementInfo As Object, codeLanguage As CodeLanguage)
 SubMain.GhostDoc.Core.DLL: N 02969
 SubMain.GhostDoc.T4.Context.Initialize(ctxtObj As Object, parameters As Hashtable, codeLanguage As CodeLanguage)
 SubMain.GhostDoc.Core.DLL: N 00652
 A.cd050f4b250007320e50fe5e958b5cd4e.c4f6b19298f078933cb0df4efa49ca6e2( As c2ea400aa07f04bd1cebc5abf5f4aeff2,  As Rule,  As MemberRuleArgs,  As Object)
 SubMain.GhostDoc.Core.DLL: N 00188
 A.c476f267f986334d5e33e073bcdbd1f86.cd822087bce47457322ab2922883a634b()
 SubMain.GhostDoc.Core.DLL: N 00765
 A.c476f267f986334d5e33e073bcdbd1f86.c0d776bf94ff22ffe18c6ef8ce5689681( As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00031
 A.c34619165aba414d27648090d62429ef1.cea20907df77db43e6a93c9c36538560e( As c2ea400aa07f04bd1cebc5abf5f4aeff2,  As TextSelection,  As Object,  As CodeLanguage,  As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00525

Log Message (11/12/2025 10:06:58 AM) : DocumentThisCommandImplementation->Run finished.
Log Message (11/12/2025 10:07:22 AM) : SendStatistics method started...
Log Message (11/12/2025 10:07:22 AM) : SendStatistics method finished

3 Replies

Reply to Thread
0
Misha Zhutov Replied
Employee Post
Hi Rick, did you provide a log from VS2026? The latest public GhostDoc build does not support VS2026 and we are working on it.
0
Rick Mathers Replied
The log I provided was an excerpt from the GhostDoc Pro.log file.  Is there a log file you need from Visual Studio as well?
0
Misha Zhutov Replied
Employee Post
From what folder is the GhostDoc Pro.log file? Did you document in VS2022 or VS2026? It is not clear what "it does not document the file as expected" means. Could you provide us with an example?

Reply to Thread