Looking for proper scripting for allowing context sensitive help with a .Net application

[Shawn_K__N_]

Hi. I am looking for help with the scripting that we should be using so that our context sensitive help works with our .Net application. The scripting we used to get the context sensitive help to work with our ASP application no longer works with the .Net application. Can anyone tell me what initial scripting we should be using to make our context sensitive help work with our .Net application? Thank you in advance.
Sincerely,
-Shawn

[Roger_N]

Shawn -

Welcome!

If you're using VBscript, the window.open() method will open a new window with a URL.

[MergeThis]

A search on .NET on the forum retrieved one of my posts on this subject from last year:

==================================================

Our developers name all forms (windows), tabs, and controls, and they call like-named WebHelp HTM files directly in a cascading drop-off style. For example, in this call for a Name drop-down selection field on the Main tab of an Admin window:

adminmainmenu.admainmaintab.admainnameedit.htm

the app looks for admainnameedit.htm first; not finding that, it looks for admainmaintab.htm next, then finally settles on adminmainmenu.htm (we're only using window-level help right now, but with all elements named we could go more granular anytime).

Because our help is a merged WebHelp project, we also place a comma-separated formpath.txt file at the root, with entries like these to denote the projects (folders) where the app will find the topics:

adminmainmenu, mergedProjects\admin


Good luck,
Leon