Unlimited plan subscription just for $150$99!

Pay with Bitcoin!

The users who experience problem with Paypal have the opportunity to upgrade their user account through transferring the subscription fee to our Bitcoin wallet and notifying us via an email.
If Bitcoin is not a suitable option for you, please feel free to contact us to get other Paypal accounts' address.Attention: Please use "User Account Upgrade" as the subject of your e-mail.

irDevelopers.com website is the largest warez resource for software developers and programmers in the world. We provide our users with the most up-to-date and Full Version .Net, Delphi, and other software development tools.To be able to download some of these tools, you need to sign up for the website and buy one of the plans available on the website.

See how easy the code commenting with XML doc comments can be with powerful comment templates and sophisticated WYSIWYG comment editor.

VSdocman - a .NET documentation compiler - is directly integrated in Visual Studio so it will assist you with complete process of creating a documentation. This includes intelligent semi-automatic commenting of your code elements, creating additional topics (non-API reference) and generating and deploying the documentation.

Based on your settings, VSdocman scans a VS project or a solution, and then it generates the final documentation. It automatically reads namespaces, types and their members. Summary, remarks, parameter descriptions and other content are extracted from XML documentation comments in your code (those that start with /// or '''). The tool will boost your productivity no matter whether you create a class library, a component, a control, an application, a web site (ASP .NET) or any other C#/VB project type.

Move your documenting to the next level

Productivity

Everything directly in Visual Studio. Save your time, effort and money. With VSdocman, you can generate documentation from the .NET XML comments with just a single mouse click.

Command line mode

What you get with VSdocman:

All in one solution. You can create complex comments, generate VS documentation and then deploy and register it. Everything directly from Visual Studio.

Professional documentation of your code can be created in seconds for your customers, clients, you and your co-developers.

Consistency. All changes in the code are automatically reflected in newly generated documentation, which is always up to date and accurate.

Documentation in various formats and languages can be produced with just a few mouse clicks.

Efficient communication within a team, especially when a source control is used (e.g. TFS, Subversion, GIT or SourceSafe). Each developer comments his part of code. Everybody in the team can then see the comments, get an on-line help and use IntelliSense tooltips to easily understand the code.

The source code is precisely commented and looks professional.

What's new in VSdocman version 7.3:

NEW: Added complete traditional Chinese translation for generated documentation. Just select zh-TW as the language in the output options.

NEW: You can specify topics version for the MS Help Viewer format. See VSdocman's help, Viewing and Deploying Documentation - View and Deploy MS Help Viewer Documentation - Topic Versions in MS Help Viewer Documentation page.

CHANGE: In web site projects without a project file (not web applications), the $(ProjectDir) macro in the output options has a different value. Previously it was the directory constructed from <SOLUTION_FOLDER>\<WEBSITE_NAME>. Now it points just to <SOLUTION_FOLDER>. So if you have a web site (not a web application with a project file) and you specified the Output folder as $(ProjectDir)VSdoc, you need to change it to $(ProjectDir)<WEBSITE_NAME>\VSdoc, where <WEBSITE_NAME> is the name of your web site project.

FIX: The links that contained an ampersand (e.g. <see href="http://www.helixoft.com/index?x=1&y=2"/>) were generated incorrectly.

FIX: The link to the parent namespace was not generated in a code member topic, if the namespace was a root namespace in the project.

FIX: In VB .NET, external methods defined with DllImport attribute instead of Declare statement were not recognized as external.

FIX: Links to external methods (defined with DllImport attribute) were not generated correctly.

FIX: If an event in VB .NET was defined with an explicit generic delegate, e.g. Public Event TextChanged As EventHandler(Of TextChangedEventArgs), the syntax section in documentation was generated incorrectly.

FIX: If a method in a class implemented a method in an interface, the comment for a method was incorrectly inherited if the interface contained multiple method overloads, i.e. methods with the same name but different parameters. This happened when you for example clicked "Add XML comment" for the method in the class.

FIX: The blank lines inside a <code> tag that were inserted in the comment editor were not included in the XML comment.