P
Peter Row
Hi,
I work on a large application (relative I guess) and the help is implemented
in a CHM file converted from a Word file.
For the version of the app pending release one of the things done was to
upgrade to .NET 2.0.
As a result it seems that pressing F1, whilst bring the help up, if you
click any related links displayed on any of the pages
then after a short period of the Windows help chm viewer being unresponsive
it generates an out-of-memory error and
clicking [ok] closes both the help and the application.
My reason for suspecting this is due to the following investigation:
1) Doc-To-Help forum (product being used to convert Word file to help chm
file) some one has virtually identical
problem (except they don't get the message and the closure, just no links
work). The single response was that it was
a .NET 2.0 framework issue.
2) If I launch the CHM from Windows explorer then links work fine.
3) If I copy the help file to the install directory of the previous version
of our app (which uses .NET 1.1) and launch
the help from the previous version then links work fine.
If anybody has encountered this problem and knows of any way around it then
that would most appreciated.
Regards,
Peter
I work on a large application (relative I guess) and the help is implemented
in a CHM file converted from a Word file.
For the version of the app pending release one of the things done was to
upgrade to .NET 2.0.
As a result it seems that pressing F1, whilst bring the help up, if you
click any related links displayed on any of the pages
then after a short period of the Windows help chm viewer being unresponsive
it generates an out-of-memory error and
clicking [ok] closes both the help and the application.
My reason for suspecting this is due to the following investigation:
1) Doc-To-Help forum (product being used to convert Word file to help chm
file) some one has virtually identical
problem (except they don't get the message and the closure, just no links
work). The single response was that it was
a .NET 2.0 framework issue.
2) If I launch the CHM from Windows explorer then links work fine.
3) If I copy the help file to the install directory of the previous version
of our app (which uses .NET 1.1) and launch
the help from the previous version then links work fine.
If anybody has encountered this problem and knows of any way around it then
that would most appreciated.
Regards,
Peter