This is something I find a bit troublesome, even with the gigabytes of hard disk space available these days. If you deploy an application using ClickOnce, the installation is done per-user, which means that each person who logs on will have to download the application from scratch which is bad enough if the download size is large. So we could end up in a situation where a single computer has several copies of exactly the same application on the hard disk. Now if the computer is used by tens or even hundreds of people, the situation would rapidly spiral out of control. The hard disk would clog up and probably the maximum cache size would be reached, stopping any more applications from being downloaded.

Am I exaggerating the situation, or does anyone else have any thoughts on this? We have a custom deployment solution that worked with .NET 1.1, but this required our users to install an additional ActiveX control as well as the .NET Framework. It would be great to move entirely to ClickOnce to reduce headache for our customers, but is this a double-edged sword?

Hami

Each app can have only a maximum of two versions.. ClickOnce scavenger will make sure of it. So you don't need to be worried about overflowing your hard disk

-Sreekanth

Each app can have only a maximum of two versions.. ClickOnce scavenger will make sure of it. So you don't need to be worried about overflowing your hard disk

-Sreekanth