ClickOnce deployment is leaving multiple versions (yes, more than two)

Question

I\'ve got a ClickOnce application that is leaving all old versions on my disk. It\'s an internal corporate application that gets frequent updates, so this is a disaster for

Answer 1

The scavenger service is part of the ClickOnce engine; it runs automatically, and isn't something you can access directly. It should be coming around and cleaning up the old versions.

Question about the min version. If you deploy new version & set min required version to new version#, does it update the app to that version? Then leaves the former one(s) on disk?

Is there any pattern that you can see? Is there a limit to the number of deployments that it is caching?

There's also something about shadow folders that is tickling the edges of my memory; the files aren't really there. I'll do a little research and look through my notes and see what I can find.

What kind of app is it? WinForms/WPF/VSTO?

When you say it is caching folders, which folder is it? For a winforms app, for example, there are two folders created for each version (xxxxtion... and xxxxexe... or something like that) plus a bunch of folders -- one for each assembly included in the deployment -- these are cached versions of the assemblies, to keep from having to download them every time if they haven't changed. Is it the xxxxtion and xxxxexe folders that you are seeing multiples of?