Rick,
Of course I know your product. What VFP guy doesn't?
I did not know it worked for .net. Cool!

Also .net is a new sandbox and I was looking for some useful best practices. I know that with XML comments you build documentation directly from VS.NET source files but I remember that only works in C#. Is this the case with your Help Builder?

I will download and re-review HTML Help Builder.

Any links to Best Practices would be appreciated.

Thanks
- jim durkin



>Hey James,
>
>My company publishes HTML Help Builder which is a tool geared at software developers to facilitate creating both end user and developer documentation. It only does HTML Help, HTML and Word, but for .Net applications that's all you can really use.
>
>The tool allows imports from a number of different sources including .Net assemblies and individual classes as well as databases from SQL Server and VFP.
>
>There's a free shareware version you can check out:
>
>http://www.west-wind.com/wwHelp
>
>and examples of help files created with it:
>
>*** Pure Developer docs
>http://www.west-wind.com/webconnection/docs
>
>*** Application and Developer combo
>http://www.west-wind.com/webmonitor/docs/
>
>
>Regards,
>
>+++ Rick ---
>
>>All,
>>What tools are people using for authoring HTML Help, WinHelp, RTF, HTML output, and printed manuals? What are some best-practice in Net?
>>
>>Specifically looking for;
>>EndUser documentation and Code/developer documentation ( Other then // )
>>
>>thanks
>>- jim durkin