Thanks for the tip - I'd forgotten I put it in clear text as I post via Newsgator. Mind you, I can't imagine any way I could get more spam than I currently do ;-)
Strong Naming:
You need to sign the assembly with a public/private key pair generated via the strong name utility (sn.exe). You execute
sn -k <keyfile name>
to generate the key pair and then sign the assembly using AssemblyKeyFile attribute (if you build with VS.NET you will find it in the AssemblyInfo.cs file). This operation changes the name of the assembly so you will have to recompile all of the components that use this assembly.
GAC
the Global Assembly Cache (GAC) is the .NET equivelent of the SYSTEM32 directory iun that if you put your component inn there all code looking for it will be able to find it. However, unlike SYSTEM32 it is not prone to different versions of a DLL overwriting eachother, multiple versions can live in there side by side. You install a component in the GAC via gacutil.exe
gacutil -i <assembly file name>
Codebase hint
A code base hint is a mapping from a strong named assembly version to a physical location for that assembly. It is put in the config file for an application (although you could also put it in the machine.config IIRC). Look at the help for the <codebase> element of an application config file. BTW: its called a hint because the assembly resolver will look in the GAC before checking for codebase hints.
Regards
Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog
http://www.dotnetconsult.co.uk
nntp://news.microsoft.com/microsoft.public.dotnet.framework/<#
[email protected]>
can you just explain in a sentense about each of the options - how it is done. and BTW becarefull from exposing your email in a clean way in the news group, you'll get junk mail soon. TIA!!!