By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,967 Members | 815 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,967 IT Pros & Developers. It's quick & easy.

Implications of Signing an Assembly

P: 1
I have a mixed code dll which will be used by many developers to build applications on top of.

I've read signing an assembly is recommended to rule out any naming conflicts, and increase security.

However I believe that signing a dll uses it version number as part of the signing process, the problem being:

If i initially released v1.0.0.0 and other developers generated applications using it, if i updated the dll to v1.0.0.1 its signature would change and the developers must recompile to use it.

Is this true?

(I'm not putting the assembly in the GAC, as it needs to be in a specific dir as the native code it contains references other dlls.)
Aug 11 '07 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.