- Is the programming required to integrate DotNet Help worth it?
- Is the added benefit of having the dynamic help windows that great?
- Has anyone been able to discern quantifiable improvements in user assistance by using DotNet help? I'd love to know.
- Can you glean any analytics from DotNet help?
- Will anyone provide specific reasons as to why they went with DotNet help over WebHelp?
- Doesn't packaging DotNet help with an application mean that you have to deal with "laggy" help updates like you might expect with the antiquated MS HTML Help (.chm) format? OR... Has anyone on these forums successfully served up .WebHelp files from a corporate server to a user's system with a DotNet help integration so as to provide timely updates?
It seems to me that from a functionality standpoint, using WebHelp (regular flavor or HTML5) would provide essentially the same benefits as DotNet help, just without the spiffy help windows. From the standpoint of doling out precious developer time, WebHelp could be maintained, developed, and deployed fairly easily by a technical communicator with a modest amount of HTML/CSS knowledge. (read: me!) Thanks!