This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
System.Windows.Forms.Help.ShowHelp(null, helpFile, HelpNavigator.TopicId, helpId);
I have to use
ShellExecute(IntPtr.Zero, new StringBuilder("Open"), new StringBuilder(helpFile), null, null, 1);
But can not goto topic Page.
Office 365 is also fail.
We're having the same problem, see https://learn.microsoft.com/en-us/answers/questions/308412/is-the-latest-version-of-excel-365-blocking-htmlhe.html
ShellExecute will work as Excel cannot block the call to the HtmlHelp API, but that is not a solution for us unfortunately.
The same problem here!
Is it a "bad" Office update? Or Windows? Are there any plans to fix it?
I hesitate to use ShellExecute ( ) for the same reason - can not open a particular topic.
Running into this too. Running as a process and using the mapid argument seems to work for now.
// Used to be Help.ShowHelp(parentForm, pathToHelpFile, HelpNavigator.TopicId, myContextId)
Process.Start("hh.exe", $"-mapid {myContextId} my-helpfile.chm");
Should I be looking for an alternative to CHM for this add-in in-case they block the process? Maybe display HTML in a task pane instead?
In Excel, at least, it might be worth trying to call Application.Help instead.
Thanks, but I hesitate to use Application.Help .
Every time Help is called from the application, Application.Help opens a new Help window.
And when user closes the application, he has to close all Help windows manually.
HtmlHelp () doesn't have these issues.
Call HtmlHelp(0, ....HelpName, &H12, 0) closes help file automatically
Ah - that is a side-effect I wasn't aware of.