Limiting Versions On Deployment Server for ClickOnce

From the sounds of this StackOverflow answer it seems that when I publish my app for our company to use internally I have to manually remove the older "versions" from [Publish Directory]\Application Files.

I'm assumi开发者_高级运维ng this is correct, but is there any consequence to doing this? I've read that ClickOnce does merging changes to application settings, but does it need the other versions for patching an upgrading app?

I'm concerned about the scenario where I have a user that has skipped upgrading for a version or two and when they do decide to upgrade the ClickOnce architecture requires that the deployment folder contain all the versions and the current most deployed version in order to upgrade.

This doesn't seem plausable to me, but can someone confirm that all I need in the folder is the latest version? Also, any help in writing a Windows task to clean out all the older versions except the most recent would be very helpful!

---

I assume you are using Visual Studio to publish. If so, every time you publish it publishes the entire application. Each published version is independent of one another. No need to keep previous versions other than having a backup around.