ClickOnce always caches assemblies in separate folders, in addition to holding them in their own deployment folder. Is this assembly strongly named? Have you put out a new version of it, and not updated the version number? How is the assembly built, and how is it included in the ClickOnce deployment?

Have you tried uninstalling the ClickOnce application and reinstalling it?

Have you tried uninstalling the ClickOnce application, deleting the \apps\2.0 folder, and reinstalling it?

RobinDotNet

---

Click here to visit my ClickOnce blog!

Robin, thank you for your reply.

This assembly is strongly named.

I have put out a new version with updated assembly version number. In deployment package there is MyAssembly.dll with FileVersion 1.0.0.0 and AssemblyVersion 1.0.3432.32440. In ClickOnce cache there is MyAssembly with FileVersion 1.0.0.0 and AssemblyVersion 1.0.2775.22152. This old version from cache used ClickOnce when installing MyApp.

Could be the same FileVersion the reason?

In MyApp.exe.manifest I have

<dependency>
<dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="MyAssembly.dll" size="472576">
<assemblyIdentity name="MyAssembly" version="1.0.3432.32440" publicKeyToken="D66DE92CB5FE9CF3" language="neutral" processorArchitecture="msil" />
<hash>
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>UldLYhv7seDY5bsREFa+Xo02MH0=</dsig:DigestValue>
</hash>
</dependentAssembly>
</dependency>

Reinstall didn't help.

Deleting \apps\2.0 folder and ClickOnces's registry keys would probably help but I cann't ask MyApp's user for doing this.

What if you make the file version the same as the assembly version? To be honest, I don't know the difference, we just always update both of them. This could be your problem.

Also, please do try what I mentioned before about deleting the cache. And also, when you say "in the clickonce cache", do you mean the folder that only contains that one dll (every assembly gets their own folder for versioning), or the one that contains all of the dll's and the exe file?

RobinDotNet

---

Click here to visit my ClickOnce blog!

I've got the exact same problem. Did you find out why this happened? I don't even update the version number of my assembly, because from what I have heard dotNet should use the hash value when checking if the assembly is updated. The hash value is updated every time you rebuild in Visual Studio.

One other thing to note is that we get different behvaiuor on different machines. So one machine could have been nicely updated while another has a reference to an old dll (assembly). This makes it even more worrying though!

This appears to be a bug with .net framework 3.5 SP1

http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/37e20cec-933a-42a6-b5a2-890ab863b0b4