JScript vsdoc Stub Generator

Free

This is a simple extension that auto-generates vsdoc comments for JScript when completing a triple-slash, similar to other languages in Visual Studio.

(4) Review
Visual Studio
2010
Download (3,726)
7/9/2013
1.2.2
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (4)
Q and A (5)
Sign in to write a review
Sort by:

by DotNetWise | April 03 2013

Get even better intellisense with this plugin
https://github.com/dotnetwise/VS2012-Javascript-Intellisense

by Alex Pearlstein | August 16 2012

Said what it does, and does what it said.

by arthurhwnd | June 29 2012

by ohaq | April 05 2012

Thank you very much for this. VS is adding more and more features to support JavaScript, I am surprised they still dont generate documentation comment template for JavaScript. Now I dont have to copy paste my js function in C# to generate the stubs.

Sign in to start a discussion


  • Question regarding the Javascript Parser used
    2 Posts | Last post March 04, 2014
    • Nice extension mate. I am implementing an extension that needs to parse javascript code using c#. Nevertheless, I can't find a javascript parser implemented in c#. I assume you had to use one to implement your extension. Can you please direct me into the right direction?
      
      Thank you
    • Hello Moe, I actually did not use a JavaScript parser for this. Everything was done manually. (There isn't a huge amount of parsing that needs to be done) However, JavaScript .NET looks promising. http://javascriptdotnet.codeplex.com/
      
      Not sure if it will do what you need, but it's worth a shot!
  • Adding Return Tags
    3 Posts | Last post July 10, 2013
    • I have currently implemented a somewhat stable return tag generator, but my question is when should a return tag actually be added?
      
      There are a few stances I can see on this:
      
      Every JavaScript function returns something:
      
      Should every function comment stub have a return tag, then, whether something is explicitly defined or not?
      
      The current implementation is unreliable in more complex code:
      
      Would it be better to leave a return tag off completely, and let the user decide, or is an educated guess good enough?
      
      The return tag is unimportant to me:
      
      The return type may not be all that critical in a lot of cases, and when it is, it isn't that big of a deal to type it in myself.
      
      Which approach would you rather I take?
      
      -Always create a return tag
      -Guess when to add the return tag
      -Never create a return tag
      -Other
      
      Thanks for your input/suggestions!
    • I would prefer that you always include the return tag.  It's easy enough to delete if it's really not wanted.  Like you said, every JS function returns something, so maybe it's appropriate to document what it returns, even if it's `undefined`.
    • Thanks for your response Joseph, I had completely forgotten about this post! I really need to bring the 2010 version of this extension up to date with the 2012 version. I have an options UI in the 2012 version, and I think it would make sense to simply add an option to determine when to add the return tag. (Always, Never, Auto)
      
      Since writing this post, I also agree Always would be better, especially if you're like me and write the comment for the function before writing the code itself.
  • Generate vsdoc xml comment in javascript code inside .aspx page
    2 Posts | Last post May 07, 2012
    • Is it possible to add comments in JavaScript code that is inside the <script type="text/javascript"> tag. Currently nothing happens. I have a dummy .js file and i copy the functions there in order to get the auto generation to work.
    • Currently, it is not possible. It is not because it would be difficult to do so, I just have not had the time to test it in an html/aspx/cshtml file, so I did not want to include it. I'll try looking into it this evening and see how it fares.
  • Issues
    4 Posts | Last post May 04, 2012
    • Post any issues you find with the extension here.
    • Yes, I am definitely replying to myself, this is as much for me to remember what needs to be fixed as to let everyone know about current issues.
      
      -Extension Crashes when no parentheses are on the same line as a function declaration
      -On Extension Crash, the file is rendered un-editable until closing and re-opening the file.
    • The issues I've mentioned above have been fixed.
    • Generate vsdoc xml comment in javascript code inside .aspx page.
      
      Is it possible to add comments in JavaScript code that is inside the <script type="text/javascript"> tag. Currently nothing happens. I have a dummy .js file and i copy the functions there in order to get the auto generation to work.
  • Support for VS11
    4 Posts | Last post March 21, 2012
    • It would be great if we could already use this in VS11 Beta. What are your plans for supporting VS11 (Beta)?
    • Now that I feel I have something stable for VS2010 SP1, that is something I would like to look into. I'll let you know more when I get a chance to look into the details of supporting VS11. Since I am new to VS extensions, I do not know if that is something that will be really quick to do, or if it will take some time.
    • Thanks Daniel, for suggesting I create the extension for Visual Studio 2011. I've created the extension page here: http://visualstudiogallery.msdn.microsoft.com/0cb7304b-ad78-4283-ba2b-42804657fcdd
      
      You can also download it through the extension manager in VS11.
      
      If you run into any issues with it, don't hesitate to mention it in the discussions on that extension page.
    • THIS IS AWESOME!
      
      Thank you very much! :-)