Hello, 

GhostDoc v2022.2.22190 works with VS2022 v17.9. The v17.10 was released 4 days ago and we did not test GhostDoc against it. We will take a look at that new version and get back to you.  

Thanks.

For future VS releases you could use the VS preview versions to be prepared:
h t t p s ://visualstudio.microsoft.com/vs/preview/

Hello, what GhostDoc edition are you using? Community or Pro?

Community.

You can download v2022.3.24150  from https://submain.com/download/ghostdoc/community/

Hello Misha,

the updated version works for methods but not for constructors. :(

It's the guarding statements:

if (something == null) throw new ArgumentNullException(nameof(something));

Application Domain: DefaultDomain
Product Version:
Assembly Codebase: file:///c:/users/someone/appdata/local/microsoft/visualstudio/17.0_94416df2/extensions/pbmwijvx.cy1/SubMain.GhostDoc.Core.DLL
Assembly Version: 2.2.0.0
Assembly Build Date: 2024-06-02 17:34:21
Assembly Full Name: SubMain.GhostDoc.Core, Version=2.2.0.0, Culture=neutral, PublicKeyToken=94c677ee32cc1929

Exception Source: mscorlib
Exception Type: System.Reflection.AmbiguousMatchException
Exception Message: DocumentMember: Ambiguous match found.
Exception Target Site: GetMethodImpl

---- Stack Trace ----
 System.RuntimeType.GetMethodImpl(name As String, bindingAttr As BindingFlags, binder As Binder, callConv As CallingConventions, types As Type[], modifiers As ParameterModifier[])
 SubMain.GhostDoc.Core.DLL: N 14550068
 System.Type.GetMethod(name As String, bindingAttr As BindingFlags)
 SubMain.GhostDoc.Core.DLL: N 00045
 A.c5b5657ddbcdd67642865c56159f93346.c0012a3cfd6f80130a0508007ae497b4b( As Object,  As String,  As BindingFlags)
 SubMain.GhostDoc.Core.DLL: N 00046
 A.cd5489c610fc2961625d6243d5bc5dfb4.ce0c89f22cfd3e2f20c888e932c0d07ef()
 SubMain.GhostDoc.Core.DLL: N 00063
 A.c6fcba48a14367e4d07cc253faa366530.cfad06d460625709c31467123b6c2d3ac( As IProjectFile,  As Object&)
 SubMain.GhostDoc.Core.DLL: N 00515
 A.c6fcba48a14367e4d07cc253faa366530.ce5fe69370809666d1400d201a3519a18( As IProjectFile,  As Object&)
 SubMain.GhostDoc.Core.DLL: N 00057
 A.c6fcba48a14367e4d07cc253faa366530.c0e85a653e753c1efe8f55802dcbbcf76( As String,  As IProjectFile,  As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00062
 A.cb5537a3e5edba2c0cce47c55b9cf89fc.c5d0f163036b5cb6c2a31646b6c697c57( As Dictionary`2,  As IMember,  As IExpression,  As IExpression,  As String,  As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00362
 A.cb5537a3e5edba2c0cce47c55b9cf89fc.c77c681bea3ed460a61eb0ed018846faf( As Dictionary`2,  As IMember,  As IExpression,  As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00550
 A.cb5537a3e5edba2c0cce47c55b9cf89fc.c485815df6b2eebe2d51c69bc90935876( As Dictionary`2,  As IMember,  As ExpressionCollection,  As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00075
 A.cb5537a3e5edba2c0cce47c55b9cf89fc.c485815df6b2eebe2d51c69bc90935876( As Dictionary`2,  As IMember,  As ExpressionCollection,  As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00153
 A.cb5537a3e5edba2c0cce47c55b9cf89fc.c485815df6b2eebe2d51c69bc90935876( As Dictionary`2,  As IMember,  As ExpressionCollection,  As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00153
 A.cb5537a3e5edba2c0cce47c55b9cf89fc.c485815df6b2eebe2d51c69bc90935876( As Dictionary`2,  As IMember,  As ExpressionCollection,  As Boolean)
 SubMain.GhostDoc.Core.DLL: N 00153
 A.cb5537a3e5edba2c0cce47c55b9cf89fc.c871afaaa49b1c07409e0380e558a76f4( As IMember)
 SubMain.GhostDoc.Core.DLL: N 00305
 A.c547df9300688318a7a725fdc09bb0306.cd822087bce47457322ab2922883a634b()
 SubMain.GhostDoc.Core.DLL: N 00133
 A.c547df9300688318a7a725fdc09bb0306.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 00321

Log Message (2024-06-08 08:29:54) : DocumentThisCommandImplementation->Run finished.
Log Message (2024-06-08 08:30:40) : Created DpiAwareness scope: True

Hello, 

The link has a reference to the GhostDoc v2022.3.24150 Community. If you need Pro or Enterprise please download and use v2024.

Could you please clarify the problem with documenting constructors in v2022 17.10? Is it possible to provide us with a code snippet that reproduces the issue? 

I've sent a separate Support request yesterday after reading this community post regarding the fact that my pro license expired in March 2024 without my knowledge. There doesn't appear to be any versions available prior to March 2024 and the previous version released as 2022.2.x . At least none that I can find.

v2022.3.xx appears to have never been released to anyone other than unpaid Community versions.

V2024.x appears to have been released in late May 2024.

I currently can't use v2024.x due to licensing issues that I am presently trying to resolve.

A code snippet seems irrelevant as it applies to every project I have - its a problem introduced by VS2022.10. Can you edit or create a comment using the comment editor and VS2022.10 and GhostDoc Pro v 2022.2.x? I can't.

Hi Glen, 

The v2022.3 was an interim build, and you wrote to the thread that another user opened. That's why it is not shown on the website. Also, we asked about the code snippet the user who opened this thread.

We will contact you in a separate support request you created.

@Misha

Write a constructor/method with a parameter, in this case "something:

public void DoSomething(string something) {

  if (something == null) throw new ArgumentNullException(nameof(something));
}

Behaves the same for constructors and I guess for any other method like code block where you can add guarding statements.

I guess the problem is located in your code where you generate the exception documentation.

Thank you, we found the issue and working on it. We will get back to you shortly.

We have already fixed the issue, please download and install v2022.3.24160 from https://submain.com/download/ghostdoc/community/

I can confirm that it works with Visual Studio 2022 v17.10.3.

Thanks!

Thank you for the update.

Can this bug be updated for v2022 of enterprise?

Hi Nick,

Please contact us via support@submain.com and we will provide you with a solution.