The help viewer (client) would always have to be on the user's computer, regardless of where the DotNetHelp file resides. The help file can be on the user's computer or a network share. To test it, install the DotNetHelp Viewer for the version of Flare you're using, then go to C:\Program Files\MadCap Software\MadCap Flare V6.1\Flare.app\Resources (replace V6.1 with whatever version of Flare you're running). Copy the Flare.mchelpf or FlareLight.mchelpf folder to a network share. Open that folder on the network share and double-click on the Manual.mchelp file. You'll see the help open in the help viewer, even though the help file is on a network share. You couldn't do that with CHM -- it can only be accessed from the user's computer.BruceMcNaughton wrote:Are you saying that the files used by DotNetHelp can be stored on a server (as in webhelp) but the UI is actually available on the client?
If yes! How is this actually done? The interface does not seem to be able to open a website? or Is there some other trick?
I don't know if DotNetHelp can be served on a web server. If it could, you'd have to provide a link to the Manual.mchelp file, but it might try to open it in the browser, which a quick test showed wouldn't work. So you'd have to somehow format the link to have the Manual.mchelp file open in the DotNetHelp Viewer, and that's beyond me. I did that once on a shortcut on Windows Explorer, but I don't know how to do the same in an URL.