[2005] Avoiding possible user.config file collisions

[esharris]

I'm developing a Visual Basic .Net application. Numerous versions of the program have user settings that put user.config files under paths of the following form.

C:\Documents and Settings\{user name}\Local Settings\Application Data\{company name}\?????\1.0.0.0

The "user name" corresponds to the sub-folder for my user account. The "company name" is the name of my company. The settings information has evolved over time. Within the "company name" sub-folder, there are numerous folders whose names begin with name of my executable

{my program}.exe

(There are a few starting with {my program}.vshost.exe.)
Following the executable file name prefix (of these sub-folder names) is a suffix that begins with "_Url_" and continues with a indecipherable sequence of letters and numbers.

Twice, I have had some version of my program crash inelegantly because it didn't recognize the input in the user.config it found. I believe one version of my program is reading the user.config file of an earlier version of my program.

So, how does Visual Basic .Net avoid possible user.config file collisions? Clearly, you don't want different versions of the same program sharing a user.config; their required contents may differ.

[Hack]

Clearly, you don't want different versions of the same program sharing a user.config;

Actually, you can end that sentence like this

Clearly, you don't want different versions of the same program

All previous versions of this program need to be removed so that everyone is using the same version. If there are config files floating around all over everywhere, they need to be cleaned up.

Also, your thread title should reflect not only the version you are using, but a brief description of the issue.

[esharris]

This doesn't answer my question.

BTW, you're taking my quote out of context. I'm not saying ...

"Clearly, you don't want different versions of the same program"

I disagree with this statement. I have VB6 and VB 2005 .Net express on the same machine. Sometimes, I want to load a colleague's VB6 program into a VB environment without converting it to VB .Net.