Geek Answers Handbook

When updating an assembly, is it best to transfer files to isolated storage?

I have a .NET 2.0 C # application that updates from time to time and the build version and file version increase. All this works great, but also interrupts the storage of xml settings files in isolated storage. (Xml files are generated by DevExpress XtraGridView.SaveLayoutToXml ())

Is there a way to copy these files from an old folder in isolated storage to a new folder. Those. from Appname \ 1.0.0.0 to Appname \ 1.0.1.0

Or is there a better place to store these xml files that will not change when the version of the application file changes?

I do not want to store these files in the .exe application folder, since the application is not allowed to write to this folder in Vista without administrator rights.

+5
source share
1 answer

If you use ClickOnce, you can use the isolated application storage with limited access .

If you do not use ClickOnce, you can get the same effect by giving your application a strong name . A strong name ensures that your assembly identifier is unique by adding a public key token and digital signature to the assembly.

+2
source

More articles:


All Articles