Clickonce & Isolated Storage

Question

Has anyone had issues with the contents of an isolated storage directory go missing or not update properly after a click once automated deployment?

It turns out that we were using AssemblyScope and the version number of our assembly was based on the current year. So as the year changed from 2008 to 2009, our assembly major version changed. — mr mo, Jan 09 '09 at 15:37

score 2 · Accepted Answer · edited May 23 '17 at 11:55

2

I believe you can find your answer on this post - ClickOnce and Isolated Storage.

edited May 23 '17 at 11:55

Community

1
1

answered Jan 08 '09 at 22:40

codeConcussion

12,739
8
49
62

score 1 · Answer 2 · answered Jan 08 '09 at 22:24

If the version of your application changes (I am uncertain exactly which version number it is) then new deployment creates a new folder for storage. There are 2 ways in which isolated storage stores the data:

Isolation by user and assembly
Isolation by user, domain and assembly

In both cases, when the assembly changes the directory changes. I do not know what the best way to keep the data between deployments is, but that is the reasoning for it.

score 0 · Answer 3 · answered Jan 08 '09 at 22:00

Go "missing" -- yes. I'm not exactly sure how ClickOnce handles updates but I've seen where a new release would not have the same data directory associated with it (or it wouldn't move the contents forward). I was able to find the old file manually and copy it forward myself when necessary so for the user's application data I required them to specify a destination that they could easily set if the app lost the link to it (which was stored in IsolatedStorage).

Clickonce & Isolated Storage

3 Answers3