Geek Answers Handbook

Deploying .NET ClickOnce and Incorrect Builds Caused After Upgrade

I have a ClickOnce application (app1) that calls DLL files from another solution (app2). I recently updated this application with one client, and a strange thing happened.

He received a new version (the publication version was correct in the Control Panel / Add or Remove Programs) of application 1, and the version of the application was correct, as checked manually in the application. But the DLL files called from the referenced solution (app2) were still old.

We deleted all the files in C:\Documents and Settings\username\Local Settings\Apps\2.0and installed again. This time there were no problems; the correct DLL files were called.

It should be noted that the version numbers in the new version are completely different, since we changed this when upgrading from Visual Studio 2005 to Visual Studio 2008. Old / new published version: 1.0.0.6/1.9.1.6.

+5
source share
1 answer

This seems to be a bug in the .NET Framework 3.5 SP1.

http://support.microsoft.com/default.aspx/kb/971052

I fixed it:

  • Removing the .NET Online Cache from the Command Line: "rundll32 dfshim CleanOnlineAppCache"
  • Remove all .NET applications that may reference the same problem assembly.
  • Install all applications again.
+3
source

More articles:


All Articles