Welcome to SubMain Ideas Forum

Do you have an idea? Do you recognize a good idea when you see one? We want to hear from you!

For bug-reporting or general how-to questions, please check SubMain Community at http://community.submain.com

+10
Completed
Serge B. (Co-founder, Product Management) 6 years ago • updated 6 years ago 0
New feature suggestion: add exception documentation into XML Comment - list exceptions raised within a method.
+5
Completed
Serge B. (Co-founder, Product Management) 6 years ago • updated 4 years ago 1
A feature to generate HTML documentation file based on solution/project XML comments
Answer
This was implemented in v4
+5
Completed
Serge B. (Co-founder, Product Management) 6 years ago • updated 5 years ago 0
Add code spelling features to GhostDoc
Answer
As we announced, our CodeSpell product will be rewritten using new code spelling engine - the same engine that in used in CodeIt.Right - and CodeSpell features will be added to GhostDoc Pro.

UPDATE: Completed in Beta 2 
+5
Completed
Serge B. (Co-founder, Product Management) 6 years ago • updated 6 years ago 0
Add IntelliSense to T4 Template Editor for GhostDoc API
+3
Planned
Charles Barest 6 years ago • updated by Serge B. (Co-founder, Product Management) 6 years ago 0

It would be cool if GhostDoc Pro would warn developers of "illegal" characters within their XML comments. 

Scenario:

Yesterday, it took me a while to figure out that the reason GhostDoc Pro errored out on my comments was that I had several code examples that used the binary '&' (ampersand operator) and perhaps should have used the HTML code '&' instead. 

Would have been great if while parsing the 100+ lines of comments and source code examples I had typed in, GhostDoc Pro would have substituted the correct XML \ HTML codes everyplace I had an ampersand. 

I know there are other scenarios (such as <code> examples of generics) that have to be formatted differently in order for the XML to remain well formed and valid. Agin, it would be a killer tool if GhostDoc Pro could make those changes or at least alert the user to the existance of an illegal character.

Kindest regards,

Charles

+3
Completed
Serge B. (Co-founder, Product Management) 6 years ago • updated 5 years ago 0
Document file should support adding the top-level file header comments (<copyright/>). Also the ability to re-write that comment to handle when the file name is changed.
Answer
UPDATE: Completed in Beta 2  
+3
Completed
Lance Do 6 years ago • updated by Serge B. (Co-founder, Product Management) 5 years ago 0
Developer can choose a menu command like "Preview the documentation" to see how his documentation will be display. There are some special characters (like &lt; &gt;..) which aren't easy to see directly from the IDE editor.
Answer
Yep, thank you. We actually have it on our list. This is linked to the upcoming Generate HTML Documentation feature but is a separate feature.
+2
Completed
Serge B. (Co-founder, Product Management) 6 years ago • updated 5 years ago 2
Consider an integration that lets you rewrite comments with spelling issues.
Answer
UPDATE: Completed in Beta 2  
+1
Completed
Serge B. (Co-founder, Product Management) 6 years ago • updated 6 years ago 0

Option to include custom dictionary into the profile/rule publishing - Enterprise Edition introduces Shared dictionary (in addition to User dictionary). Shared dictionary can be included and published for all Analysis Module users.

+1
Completed
Serge B. (Co-founder, Product Management) 6 years ago • updated 6 years ago 0

Profile Editor : enable copying existing rule instance to reconfigure it under a new name