I am creating a webhelp project to be accessed from an internal homegrown intranet app(by clicking on a help button within the app it fires up the help screens in a new window).... I published the help out to a network share however now in testing opening this from my app it takes a long time to fire up the new window...
Is there a best practice for this type of scenario?? Do I need a way to copy the help project down locally for each user? If so what is the best technique being that they are accessing the help in a webapp not a winapp?
Typically you leave WebHelp on a server and access it from wherever. That's the beauty of it.
You might begin by creating a simple shortcut or hyperlink from your desktop to open the help. Check the time it takes. If it opens really fast, you know there is an issue to be addressed with the way your application is opening it.
Helpful and Handy Links