Browse by Tags
I'm evaluating GhostDoc and would rather it didn't autocomplete my param and summary descriptions. Is there a way to shut this off?
I have a class that has 4 sets of methods that each have 3 overloads. When I generate the documentation, only one method out of each set will display descriptions. Originally I thought this may be due to the fact that I was using C#6.0 Expression body functions (as the 2 overloads delegate to the the third), but this doesn't seem to be the ...
I have a method that when I document it with GhostDoc pro (I'm evaluating it), always returns the same documentation. It is an implementation method for an interface. It does not pick up the docs from the interface. If I change the summary or parameter text, it is change to some standard. I've tried deleting and adding the method. ...
In the summary (C#) I created a list of table type. It looked like this when I wrote it.
After running GhostDoc on the file it looks like this
Why is GhostDoc changing all the formatting I did?
I have a problem with my Visual Studio 2010 builds emitting warnings for all of the undocumented public methods in Service References I have in my solution (I have many).
I expressly purchased GhostDoc Pro to put comments on all of the web services automatically.
What is the proper/quick way to do that? Also, does ...
I've introduced my own rules to extend the xml output of properties, methods, fields, etc.
As mentioned in the subject, the processor stops processing, if it hits on
a List<T> type.
Take this short code snippet as an example:
I'm running version 3.0.10340 on Win7 x64.
If I have a constructor that is initially defined as 'public' and document the ctor I get the following summary comments (as expected): /// <summary> /// Initializes a new instance of the <see cref="Class1"/> class. ...
I have just started using GhostDoc and must say that it is fantastic. Congratulations on such a simple but very useful tool.
The main benefit that I am getting from it at the moment is the ability to automatically produce xml comments for inherited members. I like to document my code as much as possible but found that I was neglecting ...
This should be on the roadmap.
Is it possible to alter settings to create the <summary> element in one line only?
Now it is created like
/// Text goes here
With this format, only the first line is visible when collapsing the comment. If the element was created like
/// <summary>Text goes here</summary>