5

I have a ClickOnce application (app1) that calls DLL files from another solution (app2). I recently updated this application at one customer and a strange thing occurred.

He got the new version (publish version was correct in Control Panel/Add or Remove Programs) of app1 and the application version was correct as manually inspected in the application. But the DLL files called from the referenced solution (app2) was still the old ones.

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

One thing to mention is that the version numbers are completely different in the new version since we changed this while upgrading from Visual Studio 2005 to Visual Studio 2008. Old / new published version: 1.0.0.6 / 1.9.1.6.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Fredrik Stigmarker
  • 116
  • 1
  • 10
  • We've seen this too! In our case it was dll's in the same solution that for some reason referred to the old ones - and guess what happened when we changed the API of that dll... No idea why, but the users usually have had the app for a while and done quite a few updates. Clearing the 2.0 folder always fixes things. – andyhammar Jun 13 '09 at 20:32

1 Answers1

3

This appears to be a bug in .NET Framework 3.5 SP1.

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

I fixed it by:

  1. Clearing the .NET Online Cache from a command prompt: “rundll32 dfshim CleanOnlineAppCache”
  2. Deinstall all .NET-applications that could have a reference to the same problematic assembly.
  3. Install all applications again.
Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Fredrik Stigmarker
  • 116
  • 1
  • 10