Comments on: Troubleshooting ClickOnce deployment issues

By: Leonardo Perez

Leonardo Perez — Thu, 12 Nov 2009 18:09:25 +0000

Hello, i have just done everything explained here.. and it worked ( i had done a lot of things before i found this post, one of them was to remove my antivirus ). After i tested i began to install the things i had removed including my antivirus.. and IT HAPPEND AGAIN !!! … so in my case i uninstall and (again) clear the registry.. so my suggestions is that if u are using Clickonce.. stay away from avg antivirus ( free version in my case ).

By: Paul G

Paul G — Tue, 22 Sep 2009 01:03:19 +0000

Thank you! It’s been driving me crazy for weeks. I have a click once application deployed to over 150 users, and over the last 2 years not a problem. All of a sudden, one by one, each started to fail on update with “The referenced assembly is not installed on your system” error. Funny thing is, there was no pattern to the failure or version at which the updates stopped. To top it off, the application refused to uninstall. IT support for this client is provided from overseas, so I think that they have been updating the .NET Framework version on individual machines. I build the app on Vista and it is deployed to Win XP. Anyway, clearing the Apps\2.0 cache folder, calling ClearOnlineAppCache (using the COM component available in the framework), clearing the Deployment registry key, and clearing the registry keys listed in solution #2 has solved the problem.

By: GeekTieGuy

GeekTieGuy — Thu, 06 Sep 2007 00:31:13 +0000

Good question. I can’t speak for Microsoft, so I can only give you my guess. It probably has to do with the complexity of checking timestamps/file contents and whatnot. Checking the version number is a well-defined, relatively reliable, non-ambiguous way of doing things. If you’re using Visual Studio, you can tell it to increment the version number automatically every time you publish your files, so it’s not too much of a headache for me personally. It doesn’t even have to be a major or minor version change, it can be all the way down in the revision group (1.0.0.xyz). I’d ask the question on the Microsoft MSDN forums, if I were you.

By: Howard

Howard — Wed, 05 Sep 2007 21:47:05 +0000

Hi, maybe this is a newbie question but why does .NET require to increment the version number on everytime an application is deployed via clickonce? This is very annoying especially when I make a test version multiple times; but maybe there is some reasonable explanation. Why can’t .NET recognize the new files and without generating a new version number and filling the cache up?