Strong Naming/signing

[Techno]

What is the procedure to Strong Name/sign an assembly?

I have managed to create a strongname key using sn -k keyfile.snk

I added this in the assemblyinfo.cs:

[assembly: AssemblyKeyFile("..\\..\\keyfile.snk")]

I then compiled the project, compiled fine. Now what?

[jmcilhinney]

The point of strong-naming is to uniquely identify your assembly. No-one can substitute another assembly or edit yours and pass it off as the original. That way no-one can change the way an application works without the user knowing. If the system can't find an assembly with the specific strong name it's looking for then it will not run the app, even if it finds an assembly with the same name, size and interface. That adds a level of security against hackers who would try to change the way an application works by substituting or editing existing assemblies.

The main thing to note now is that if your assembly has a string name then all the assemblies it references must also have string names. You can't trust an assembly your using if it can't trust the assemblies it's using.

[Techno]

I do require this Is the procedure I have written done correctly or do I need to do something else?
I require this to comply with one of the SDK's I am using

[mendhak]

Use it. If you want to go the extra step, do a search on code access security (caspol.exe) and you could also place it in the GAC.

[jmcilhinney]

Are you using VS 2005? Please assume that it is ALWAYS necessary and specify your version in EVERY thread. If you are then you don't need to muck about with any code. Just open the Signing tab of the project properties and click the appropriate box. You can then create a new key file or select an existing one.

[Techno]

Thanks, this is for .NET 1.1 (VS2003)