Clickonce and Isolated Storage
If the version of your application changes (I don't know exactly what version it is), then the new deployment creates a new storage folder. There are two ways that isolated storage stores data:
- User and assembly isolation
- User, domain, and assembly isolation
In both cases, when the assembly changes, the directory changes. I don't know what is the best way to preserve data between deployments, but those are the arguments.
source to share
Go "missing" - yes. I'm not entirely sure how ClickOnce handles updates, but I've seen where the new version won't have the same data directory associated with it (or it won't move content forward). I was able to find the old file manually and copy it forward when needed, so for the custom app data, I required them to provide a destination that they could easily set if the app lost a link to it (which was saved in IsolStorage).
source to share