Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Clickonce Application Folder
 

Clickonce Application Folder

Hi,

We arerunning a clickonce application that is set tobe only available online. The application works fine,until an upgrade is done on the servers.Theproblem is that, the clients are unable to run the application after the upgrade is performed.We found that deleting the'Local Settings/Apps/2.0' folder, then having the client run the application again from IIS works. Is there a way to get the application to workwithout having to delete the application folder after each deployment?

Any help will be greatly appreciated.

I am using C# in VS2008. Application is runningfrom twoweb servers load balanced, inwhich we deploy to one server than copy the deployed folder to the other server. Server OS is windows 2003.

kirklynk  Monday, August 17, 2009 4:56 PM
The problem is that you are moving the deployment. The installation URL must match the location of the deployment. If you have the deployment on multiple servers, the user must use the same server repeatedly. The location of the deployment is part of the identity in the manifest, and if it changes, ClickOnce no longer recognizes it as the same application.

This is part of the ClickOnce application security, which keeps someone from hijacking your application and substituting files from their own location for yours.

What are you trying to do with the multiple servers? To move the deployment to the second server, you have to change hte installation URL in the manifest and re-sign it with Mage or MageUI.

RobinDotNet
Click here to visit my ClickOnce blog!
RobinDotNet  Tuesday, August 18, 2009 7:19 AM
Hello,

Thanks for your posting on MSDN forum.

>Application is runningfrom twoweb servers load balanced, inwhich we deploy to one server than copy the deployed folder to the other server. Server OS is windows 2003.

If you just copy the deployed folder to another server, that the reason why the clickonce application doesn't.As ClickOnce can provide automatic application updates. AClickOnce application periodically reads its deployment manifest file to see whether updates to the application are available. Since you just copy the deployed folder, the ClickOnce application might not be able to get there information.

If you want the ClickOnce deployment on different server, I recommend you publish the application to the different server With Visual Studio. Another choice is that you can try with MAGE or MAGEUI tool to manually deploy the application.

http://msdn.microsoft.com/en-us/library/xc3tc5xx.aspx
http://msdn.microsoft.com/en-us/library/bb384246.aspx

Thanks,
Rong-Chun Zhang
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg@microsoft.com

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
Rong-Chun Zhang  Tuesday, August 18, 2009 7:59 AM
The problem is that you are moving the deployment. The installation URL must match the location of the deployment. If you have the deployment on multiple servers, the user must use the same server repeatedly. The location of the deployment is part of the identity in the manifest, and if it changes, ClickOnce no longer recognizes it as the same application.

This is part of the ClickOnce application security, which keeps someone from hijacking your application and substituting files from their own location for yours.

What are you trying to do with the multiple servers? To move the deployment to the second server, you have to change hte installation URL in the manifest and re-sign it with Mage or MageUI.

RobinDotNet
Click here to visit my ClickOnce blog!
RobinDotNet  Tuesday, August 18, 2009 7:19 AM
Hello,

Thanks for your posting on MSDN forum.

>Application is runningfrom twoweb servers load balanced, inwhich we deploy to one server than copy the deployed folder to the other server. Server OS is windows 2003.

If you just copy the deployed folder to another server, that the reason why the clickonce application doesn't.As ClickOnce can provide automatic application updates. AClickOnce application periodically reads its deployment manifest file to see whether updates to the application are available. Since you just copy the deployed folder, the ClickOnce application might not be able to get there information.

If you want the ClickOnce deployment on different server, I recommend you publish the application to the different server With Visual Studio. Another choice is that you can try with MAGE or MAGEUI tool to manually deploy the application.

http://msdn.microsoft.com/en-us/library/xc3tc5xx.aspx
http://msdn.microsoft.com/en-us/library/bb384246.aspx

Thanks,
Rong-Chun Zhang
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg@microsoft.com

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
Rong-Chun Zhang  Tuesday, August 18, 2009 7:59 AM
I didn't notice that Robin had replied to this thread.

Thank you Robin for your effort on ClickOnce forum. You are the most valuable asset in the forums!

Thanks,
Rong-Chun Zhang
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
Rong-Chun Zhang  Tuesday, August 18, 2009 8:11 AM
Thank you Rong-Chun, I appreciate that!

Robin
Click here to visit my ClickOnce blog!
RobinDotNet  Tuesday, August 18, 2009 5:54 PM
Thanks guys.

The repliesare greatly appreciated and this information is'nice to know' for those who areusing ClickOnce applications.
kirklynk  Wednesday, August 19, 2009 2:27 PM

You can use google to search for other answers

Custom Search

More Threads

• Deploying changed User.Config or App.Config via VS2005
• Bootstrapper for exe installer
• Help with bootstrap installation
• MSI not in Add/Remove Programs
• Custom Action before install
• Windows service setup problem
• System.BadImageFormatException executing Custom Action in setup project
• Excluding files from setup project (VS2005)
• Installer throws exception
• Allow Click Once Deployment only for registered Users