Home/ Questions/Q 75995
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T20:36:14+00:00

I’m upgrading an app with many different settings files from XP to Vista and

  • 0

I’m upgrading an app with many different settings files from XP to Vista and changing location of the files to use the

Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData)

line rather than write to application path. There are values used in mannnny places from property settings. Those values are getting assigned from values in the other settings files.

I’ve been told that Microsoft will drop support for the virtualization of the writes to Program Files which is fine and is why I am upgrading…

Would a statement like the one below cause an error during runtime or need to be handled in a certain way in Vista?

Properties.Settings.Default.Properties['ConnectionString'].DefaultValue = config.ConnectionString;

I’m thinking that it would assign the values during runtime and be unable store the values in the Program Files space and would probably write it to the VirtualStore? For right now this would work but when the virtualization is removed will it still work?

I’m unsure and don’t want to proceed without asking first. I could be entirely off altogether. Any help or comments would be appreciated. Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. We are using ClickOnce here on XP and Vista and we do not have any problem. Of course, with ClickOnce the application reside on the Document Settings of the user and this might be different for your case. But, I think the ClickOnce experience from me, may give you a partial solution.

    Here is a link from someone that have using App.Config (writting) on Vista. It say that it’s not a good idea to try to write to the App.Config. Here is the 2 suggestions that he proposes:

    • use a .settings file, it gives you strongly typed settings and user/app scope per property, saving and property change notification

    • register the AppSettings section under a different name (let’s say ‘userSettings’) in app.config and specify allowExeDefinition=’MachineToRoamingUser’ for it. This allows you to keep the existing syntax.

    • 0