During development process you will need strong name keys to be exposed to developer which is not a good practice from security point of view.In such situations you can assign the key later on and during development you can use delay signing.
Delay signing allows you to place a shared assembly in the GAC by signing the assembly with just the public key. This allows the assembly to be signed with the private key at a later stage, when the development process is complete and the component or assembly is ready to be deployed. This process enables developers to work with shared assemblies as if they were strongly named, and it secures the private key of the signature from being accessed at different stages of development.
More you can find out in this link:
http://msdn.microsoft.com/en-us/library/t07a3dye.aspx
Delay signing allows you to place a shared assembly in the GAC by signing the assembly with just the public key. This allows the assembly to be signed with the private key at a later stage, when the development process is complete and the component or assembly is ready to be deployed. This process enables developers to work with shared assemblies as if they were strongly named, and it secures the private key of the signature from being accessed at different stages of development.
More you can find out in this link:
http://msdn.microsoft.com/en-us/library/t07a3dye.aspx
No comments:
Post a Comment