nutrino149
asked on
Including .chm file in deployment setup.exe
I have a working vb.net application that I can build and run. I included a .chm help file.
The problem is this, I could see it coming.
In my application I set the help provider HelpNamespace to the path for my .chm file.
That is fine on my test machine, I have when I build
.exe
.chm
and a aplication.exe.config file that has inside it
add key="HelpProvider1.HelpNam
Unfortunately, when I try to create a deployment setup.exe file it will do an install but when I try to run the program it fails with
"Additional information: The key 'HelpProvider1.HelpNamespa
This makes sense because the setup does not create a config file which is where the HelpNamespace path exists.
So my question is how do I make a deployment setup for an vb.net application that has a helpProvider pointing at a .chm file??
or
How do I include the .chm in my deployment and the executable can find it?
Thank you.
The problem is this, I could see it coming.
In my application I set the help provider HelpNamespace to the path for my .chm file.
That is fine on my test machine, I have when I build
.exe
.chm
and a aplication.exe.config file that has inside it
add key="HelpProvider1.HelpNam
Unfortunately, when I try to create a deployment setup.exe file it will do an install but when I try to run the program it fails with
"Additional information: The key 'HelpProvider1.HelpNamespa
This makes sense because the setup does not create a config file which is where the HelpNamespace path exists.
So my question is how do I make a deployment setup for an vb.net application that has a helpProvider pointing at a .chm file??
or
How do I include the .chm in my deployment and the executable can find it?
Thank you.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Actually,it was stupid of me. I have done mostly asp and a aspx applications.
The .chm help file I made with micorsofts HTML Help Workshop and included into my application was application.exe.config that has the
add key="HelpProvider1.HelpNam
Well the easy answer was I just set the help provider value to just the application name and making sure my deployment sollution included the
application and .chm and config all in the same directory (if that makes sense).
So I just needed to deploy everthing in the same folder and not try to path to the .chm file.
Oh well, live and learn.