-
My code is pretty well documented already with xml But when it comes to methods with only a xml Is there a way to suppress the output for properties with a missing |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Could you please share the XML documentation for the function shown in the screenshot you provided? |
Beta Was this translation helpful? Give feedback.
-
Of course! Here's an excerpt of the code. XML documentation was done in Visual Studio. namespace Balsam
{
/// <summary>
/// Encapsulates information about a datasource, typically from a call to a BarServer.
/// </summary>
public class DataSource : ICloneable
{
/// <summary>
/// Gets the type of BarServer used.
/// </summary>
public string BarServer { get; set; }
/// <summary>
/// Loads a json text file representation.
/// </summary>
/// <param name="fileName"></param>
/// <returns></returns>
public static DataSource Load(string fileName)
{
var json = File.ReadAllText(fileName);
return JsonConvert.DeserializeObject<DataSource>(json);
}
}
} I'd love for the Property Value output to just report the type But I did just discover in writing this response if I put in an empty /// <summary>
/// Gets the type of BarServer used.
/// </summary>
/// <value></value>
public string BarServer { get; set; } It's not ideal since Visual Studio seems to rely primarily on the Thank you @BattlefieldDuck! Your help has gotten me very close to a documentation site I can be proud of. |
Beta Was this translation helpful? Give feedback.
-
Navigate to the .parameters dd {
display: none;
} This rule will hide all
Update the template section as follows: "template": [
"default",
"modern",
"template"
], After these changes, your documentation should reflect the new styling rules. Remember to rebuild your documentation for the changes to take effect. |
Beta Was this translation helpful? Give feedback.
-
Hi @BattlefieldDuck. I can confirm that your CSS rule does the trick. Now to back out the 200 empty |
Beta Was this translation helpful? Give feedback.
Hi @BattlefieldDuck. I can confirm that your CSS rule does the trick. Now to back out the 200 empty
<value>
tags I added to public properties in my brute force attempt at fixing the problem. Fortunately, it's far easier to revert the changes than it was to add them! I'm in good shape now thanks to all your help.