If I want to build a shared assembly, does that require the overhead of signing and managing key pairs? If so, is there a best practice approach to doing so?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I want to build a shared assembly, does that require the overhead of signing and managing key pairs? If so, is there a best practice approach to doing so?
No, to share an assembly between applications (outside of the GAC which I don’t recommend that you place it in), you don’t need to sign it. You need to sign an assembly generally, when you are going to give it to a third party. Its a way of verifying the assembly is genuine and hasn’t been tampered with.
On Signing Assemblies and Best Practices
Remember this does not mean that they share the same assembly in memory. They will have their own copies and will act independently of each other. To share information between applications, you need to use either Remoting or WCF.