Per Solution Properties
Question asked by Steve Bush - February 13 at 7:52 AM
Answered
I have customized the file header rule template to include an online reference to a License file hosted in a GitHub repository. The online reference changes per solution. I have not found a way to have a per solution property that I can use to populate the licensing information.  
 
A couple of ideas.  Adding per solution properties that I could set in GhostDoc options. Another option would be to allow access to build properties.  For example, I have a build property called PackageLicenseUrl that I set in Directory.Build.props that I use to inject the license URL into package definitions.
 
There may be an existing solution but I could not find it.  
 
Thanks.
 
Steve

1 Reply

Reply to Thread
0
Serge B. Replied
Employee Post Marked As Answer
Hi Steve,
 
Thanks for the suggestion, we are currently working to improve the solution level override for most any GhostDoc setting.
 
While we are working to make it easier to use the override, I want to let you know that GhostDoc already is looking at the solution properties first and doesn't find the value override, will use it, otherwise, it will use the product wide setting.
 
You also can add any custom setting in the GeneralProperties section of the *.sln.GhostDoc.xml file and then use it in a rule template using the Context.GetSettingsValue method.
 
You can see example with the UseInheritdocTag parameter in the Method template.
 
Thanks!
Serge Baranovsky
SubMain Software
(800) 936-2134

Reply to Thread