DenaMP
asked on
Deploying vb .net windows production version app while development version still being tested by users
I am using ClickOnce Deployment with automatic updates before the application starts for a vb .net windows app. My problem is that I need to temporarily leave the test version of the app on all the machines on which I'm installing the production version. The development app is intalled from the development server and the production app is being installed from the production server, so I can't just make the production app the next revision #. I tried to rename the app but there were so many components to rename that the whole app was out of sync. Can I just override the installation path or are there internal registries that will step on each other? Any help will be greatly appreciated!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You need to use mage.exe and then resign the manifest files after you make the changes....you can make them manually but you will still need to resign the manifest.
Best Wishes.
Best Wishes.
ASKER
How do you resign the manifest?
use mage.exe with the "-sign" parameter and the "-certfile" parameter. Here's the MSDN article link:
http://msdn.microsoft.com/en-us/library/acz3y3te.aspx
http://msdn.microsoft.com/en-us/library/acz3y3te.aspx
ASKER
Thanks loads for your help! I won't have a chance to try this out until next week but I guess I'll holler if I run into a glitch.
NP DenaMP, just let me know if you run into a glitch.
Best Wishes.
Best Wishes.
ASKER
tags was in the appName.exe.manifest file, but when I tried to change the AppName as you suggested and run the set up, I got a signature error --
+ Manifest XML signature is not valid.
+ The digital signature of the object did not verify.
which of course makes sense because I changed the manifest. So, how can I change these fields in the project itself before deployment. Once again, thanks for your time and help!