I'd like to deploy a ClickOnce application, but would like to have a configurable user file to store settings and preferences that does not get overwritten everytime I publish a new version. Is there to specify that a particular file should get deployed in any installation that doesn't already have one, but not overwrite any previous versions?
The only workaround that I can envision is to store the data in a database, but it's so user-centric that it seems like a lot of overhead to re-invent the config file.