|
I signed my app with a new key and nowthe clients cannot see the new updates.
I have a problem with one specific user.
So I lethim uninstall the app from the control panel and download the new version.
The problem is the download completes adn then it opens the old version.
I do not understand why that happens, anyideas how to fix it?
How can I completely remove any files and references to the old app?
| | Dewald Viljoen Monday, April 20, 2009 2:08 PM | If you change the certificate that you are using to sign your application, it will require your users to uninstall and reinstall the application if you are not deploying the .Net 3.5 framework as a prerequisite or if you have any users running Windows Vista. Just FYI. For that one user, have him uninstall, and then delete all of the folders in his ClickOnce cache, or if he has other ClickOnce apps, you can try deleting the folders that belong to your app. I'm talking about the Apps\2.0 folder. Just delete it (if you can.) on XP, it's under Documents&Settings\username\LocalSettings\ on Vista, it's under Users\username\AppData\Local\ RobinS. http://robindotnet.wordpress.com - Marked As Answer byLinda LiuMSFT, ModeratorFriday, April 24, 2009 7:55 AM
-
| | RobinDotNet Tuesday, April 21, 2009 5:46 PM | If you change the certificate that you are using to sign your application, it will require your users to uninstall and reinstall the application if you are not deploying the .Net 3.5 framework as a prerequisite or if you have any users running Windows Vista. Just FYI. For that one user, have him uninstall, and then delete all of the folders in his ClickOnce cache, or if he has other ClickOnce apps, you can try deleting the folders that belong to your app. I'm talking about the Apps\2.0 folder. Just delete it (if you can.) on XP, it's under Documents&Settings\username\LocalSettings\ on Vista, it's under Users\username\AppData\Local\ RobinS. http://robindotnet.wordpress.com - Marked As Answer byLinda LiuMSFT, ModeratorFriday, April 24, 2009 7:55 AM
-
| | RobinDotNet Tuesday, April 21, 2009 5:46 PM | I have a customer who isseeing the same symptom as Dewald -- after uninstalling the previous version of the ClickOnce app andinstalling the next version into the IISvirtual directory, the old version continues to load. This is on Windows Vista Business SP1, both Japanese and English editions. The app is being run on the same computer as IIS, although thatwon't necessarily be true for all users.
This is an online-only app, and .NET 3.5 is not needed.
In the ClickOnce cache, we see folders for both versions. In the folder for the new version, the manifest lists the new version string but the actual exe file in the same folderis the old version.
The workaround of deleting all of the folders in the ClickOnce cache solves the problem, but that isn't feasible for commercial use -- our customer supplies our software to their customers all over Japan.
Two questions:
- Is this problem specific to Vista? I haven't been able to reproduce it on XP or on Windows 2008.
- Is there any way to prevent it, rather than manually fixing it after the fact?
Jay Freedman
http://jay-freedman.info | | J Freedman Tuesday, June 30, 2009 6:42 PM | Are you still having this problem, or have you figured it out? RobinDotNet
Click here to visit my ClickOnce blog! | | RobinDotNet Friday, July 31, 2009 7:55 AM | I am having a similar problem. But didn't change any keys, which sign assembly, yet new version does not install. This is what I changed: in Visual Studio-> Project Properties-> Application-> Assembly information -> Title and Product Name Would changing those fields require customers to reinstall app? And also, I am deploying from Visual Studio directly, so assembly is signed using my administrative credentials (according to http://msdn.microsoft.com/en-us/library/142dbbz4.aspx), is there a way that the key I used to sign assembly was changed automatically? Let'ssay when certificate lease expired and was renewed from Active Directory? | | jhhhj Wednesday, September 02, 2009 5:46 PM | Did you change the assembly name? The one in the Application tab? This would force a reinstall. Have you tried changing the Assembly information back and seeing if it makes a difference? I don't think the title would matter, I'm not sure about the product name. You could deploy an app, install it, change just those properties and redeploy it and then run the one you installed and see if it makes a difference.
The link you provided is to the general ClickOnce overview information. I don't know what "signed using my administrative credentials" means. Visual Studio will sign your deployment with whatever file you have selected in the Signing tab. SO unless you went in and changed that, it wouldn't matter. You can tell by looking at the public key token in the .application files for the two different versions.
RobinDotNet
Click here to visit my ClickOnce blog! | | RobinDotNet Saturday, September 05, 2009 6:02 PM |
|
index > ClickOnce and Setup & Deployment Projects > Cannot install a new click once version.