Strong Name Interpretation

JaedenRuiner

Well-known member
Joined
Aug 13, 2007
Messages
340
Programming Experience
10+
Well,

When you use the sn.exe tool it creates an SNK file, which you can use for a strong name key file of an assembly. By using the SNK file you can also have that strong name key file built into a ILMerged assembly executable, should it be prudent to do so.

Now, for the process of MySettings, the user.config file is saved in a very unique location. Specifically:
C:\Documents And Settings\%USERNAME%\Local Settings\Application Data\%Company Name%\%ProgramName%_StrongName_(blah)\%AssemblyVersion%

now, determining the assembly version as well as the other things are pretty straight foward, but given say an update or an installation, or no matter the reason because in truth i just want to know how, the why is inconsequential, but how does that Strong key file name get computed into that (blah) string above.
Example:
RexamClean.exe_StrongName_cadninxn5l3yxjsagxaqwat2ra5utq4w

Where does it read this, find this, compute this, and how might I do the same.

Thanks
 
I think the "(blah)" part is a random string (like temp file names and guids), probably generated when the app was added to ClickOnce application cache during install.
The difference between strong named assemblies and those not for that path appears to be only this part "_StrongName_" or "_Url_".
 
I think the "(blah)" part is a random string (like temp file names and guids), probably generated when the app was added to ClickOnce application cache during install.

Okay, but it isn't being installed with ClickOnce. This is just the natural setup for the My.Settings User.Config file. Is there a way that I can control that location in the my.settings object?
Thanks
 
Further research return this: Cool Client Stuff : Client Settings FAQ
That user.config path is given by the Configuration system, the part you asked about is called "Evidence Hash", which I have found no further info about (including looking into lots of Reflector code). Good "security, isolation and robustness" so far :)
 
Back
Top