Clickonce is the same publication version, but the assembly version is different, the update does not occur

Question

I deployed the clickonce application, in my application I have 10 external DLLs. As the code inside my dll files keeps changing, and it's hard to redistribute, I went with a clickonce deployment strategy. But I wanted to know something, if I make changes to one of the dll files and update its build version from 1.0.0.0 to 1.0.0.1, but do not change the publication version, it is still 1.0.0.0. I also set the update setting before downloading the application. I started the deployment of the installation, but did not complete the updated build. What's wrong? I am using VS2008 and C # .NET 2.0

Answer 1

ClickOnce only cares about publishing a version for the entire project. Increase this value in the "My project" tab and publish again.

Answer 2

I want to add Tom to the answer .

He's right, ClickOnce only cares about the publication version for the project. However, as soon as your application runs on the client machine and it recognizes its not the latest version, it starts comparing the hash files from the application manifest (the application manifest is one that does not have the extension “.application” ... go figure), therefore it loads only files that have been modified; yes, recompiling without changing the code is still a change.

And one last point. The progress bar that appears when the client downloads the latest version always shows the full size of your application. However, be sure that this is only downloading modified files. I checked with a bandwidth monitor to confirm it.