I have an application that is deployed using click-once. There are optional components to the deployment that are downloaded later depending on user configuration.

The optional components only seem to change on every other update of the click-once application, otherwise I just get the copy of the optional components from the click-once cache.

Any suggestions why this might be?

ClickOnce does incremental updates. This means when doing updates, it checks to see if the file has changed, and if it hasn't, it copies it from the cache rather than from the server.

RobinS.

GoldMail.com

ClickOnce does incremental updates. This means when doing updates, it checks to see if the file has changed, and if it hasn't, it copies it from the cache rather than from the server.

RobinS.

GoldMail.com

Thanks, but I'm aware of that. Even when the main project is rebuilt with changes anda new file version number, and the included dlls for the filegroup are rebuilt with changes and a new file number, the filegroup files are copied from the cache on every other install of the application. I've seen issues where an internet cache is providing an incorrect version, but the optional files are copied across from the previous version of the application, well before the filegroup would be downloaded anyway.

Okay, I have to admit, that's odd.

When you say it is happening on every other install, I'm assuming you mean updates and not full installations. Is it random, or is there a pattern to it? Are you reversioning those assemblies? Did the files that you are trying to redeploy actually change?

RobinS.

GoldMail.com

This sounds like the same caching problem that others have reported here with their internet provider. I would check with whoever is hosting your application and see if they are caching the files and not updating them right away. I have never seen this behavior with ClickOnce.

If you can run IIS on your machine, try deploying it locally, change something, deploy it, repeatedly. Install it locally the first time, then run the app to pick up the updates and see if it works. I'd bet this will be successful.

To deploy it locally, set the publishing file location to http://localhost/yourappname. You can use that url to install it on the same machine. I actually test the installation on another machine on my network by specifying the installation url as well, and fill in the IP address instead of 'localhost', like this: http://123.456.788.999 /yourappname, where 123.456.788.999 is the ip address of the machine I'm running IIS on.

Give this a try, and it will clarify where the problem is.

RobinS.

GoldMail.com