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!  
DenaMPAsked:
Who is Participating?
 
nhenny2009Connect With a Mentor Commented:
I've done this...our ClickOnce app, when deployed to our customer sites could be used by more than one group and the ClickOnce app needs to be installed twice (or more).  This will allow two revisions to be installed in the same Windows profile.

Your case is easier, because you have two different servers involved (each holding a DEV or PRODUCTION version of your ClickOnce app).

On your DEV server:
1.Deploy your app with a MyAppName.application that contains a
<assembly><assemblyIdentity name="MyAppNameDEV.application"...

Also change the assemblyIdentity under the <dependency> tags to
<assemblyIdentity name="MyAppNameDEV.exe"...

On your PRODUCTION server:
1.Deploy your app with a MyAppName.application that contains a
<assembly><assemblyIdentity name="MyAppNamePROD.application"...

Also change the assemblyIdentity under the <dependency> tags to
<assemblyIdentity name="MyAppNamePROD.exe"...


Please note...you are not actually changing the name of the executable you are deploying, rather you are only changing the "identity" of your ClickOnce executable and this is what allow you to install both even if they have the same ClickOnce revision.

Best Wishes.








0
 
DenaMPAuthor Commented:
Thanks so much for your reply.   The only place where I found the  <assembly><assemblyIdentityname
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!  

0
 
nhenny2009Commented:
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.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
DenaMPAuthor Commented:
How do you resign the manifest?  
0
 
nhenny2009Commented:
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

0
 
DenaMPAuthor Commented:
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.  
0
 
nhenny2009Commented:
NP DenaMP, just let me know if you run into a glitch.

Best Wishes.
0
All Courses

From novice to tech pro — start learning today.