G
Graham Charles
Since the .config file that contains the values in My.Settings is saved
to...
%USERPROFILE%\Local Settings\Application
Data\<companyname>\<appdomainname>_<eid>_<hash>\<verison>
....that implies that if I update the AssemblyVersionAttribute (make a
new build, say), my users' configuration files will no longer be valid.
Does that sound right? Seems like an odd default behavior. I suppose I
could manually copy the .config file during the upgrade installation,
but... well, it just seems silly.
Also, in a related question, the <companyname> in the above path seems
to have spaces replaced with underscores. Is that a documented
behavior, too? I can't find it in the SDK.
Thanks,
g.
to...
%USERPROFILE%\Local Settings\Application
Data\<companyname>\<appdomainname>_<eid>_<hash>\<verison>
....that implies that if I update the AssemblyVersionAttribute (make a
new build, say), my users' configuration files will no longer be valid.
Does that sound right? Seems like an odd default behavior. I suppose I
could manually copy the .config file during the upgrade installation,
but... well, it just seems silly.
Also, in a related question, the <companyname> in the above path seems
to have spaces replaced with underscores. Is that a documented
behavior, too? I can't find it in the SDK.
Thanks,
g.