Re: Method description thingy...

While your product looks fine... why pay? The VBCommenter power toy add-in does it for free. Coupled with (the also free and fantastic) NDoc, I can't see your product being a compelling alternative in the slightest.

There's always reason for commercial products. If you are doing basic things, free tools may be OK. Our VBdocman offers several additional features:
1. All in one.
2. More output formats.
3. Redistributable command line tool that easily registers and integrates your component documentation on user's machine during installation.
4. WYSIWYG comment editor. You can visually place bold, italic, underline, links, tables, pictures, lists and other things directly to your XML comments. It allows you to insert complex code examples and automatically escapes all dangerous XML characters.
5. While not perfect, it works as it should (unlike free tools). For example see http://groups.google.com/group/microsoft.public.dotnet.languages.vb/browse_frm/thread/bee456b3a499b6be
or
http://groups.google.com/group/microsoft.public.vstudio.helpauthoring/browse_frm/thread/70c25ee4b401da6
6. Support for generics and partial classes (in the upcoming version which will be released in a few days).
7. Conditional inclusion of members in resulting documentation, ability to include source code, ability to document namespaces.
8. Recognizes @-style javadoc comments which is very important for teams that ported their VB6 code to .NET.
9. Ability to use short numerical file names to avoid OS limit on path length and more.
10. Support.


--
Peter Macej
Helixoft - http://www.vbdocman.com
VBdocman - Automatic generator of technical documentation for VB, VB ..NET and ASP .NET code
.

Relevant Pages

  • Re: Swing Migration from SBS 2003 to new SBS 2003 box
    ... If a typical migration used to ... You can swing from a plain old NT4 non-Exchange domain to a 2003 ... Microsoft offered nothing like this in the form of documentation, ... they did not want to support the process I had outlined, ...
    (microsoft.public.windows.server.sbs)
  • Re: Swing Migration from SBS 2003 to new SBS 2003 box
    ... If a typical migration used to ... You can swing from a plain old NT4 non-Exchange domain to a 2003 ... Microsoft offered nothing like this in the form of documentation, ... did not want to support the process I had outlined, ...
    (microsoft.public.windows.server.sbs)
  • Re: Umove to Migrate SBS to new hardware
    ... Anyone interested can ask around to get opinions on Swing Migration from ... In my documentation, I cite background KBs and whitepapers constantly to ... support, even if I was walking them through the ADMT paper or something else ... provided a proper tool to migrate SBS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: ASP .NET 2.0 Unanswered questions...
    ... can you provide any documentation to support your results? ... upset towards me when all I've done is present more evidence and logic to support my case. ... I think it's a matter of deductive reasoning and facts. ... I've told you that for five years now, I've used the code-behind model ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Migrating from SBS 2000 to SBS 2003 onto new hardware
    ... First, you posted a request for Swing Migration, but perhaps you didn't know ... Microsoft offered nothing like this in the form of documentation, ... they then or will they now provide you support in doing a "Swing Migration". ... "Microsoft Small Business Server 2003 Advanced Best Practices" ...
    (microsoft.public.windows.server.sbs)