You can find some good information on the signing issues here http://nuget.codeplex.com/discussions/247827 http://blog.markrendle.net/2011/03/01/simple-data-0-5/ http://codebetter.com/sebastienlambla/2011/01/05/strong-naming-assemblies-and-openwrap/
Signing the project forces that all assemblies are signed, which no doubt you are running into. Not to mention the upgrade issues that are mentioned in the links above. Nathan Palmer On Wed, Sep 21, 2011 at 6:05 AM, Gerke Geurts <[email protected]> wrote: > Nathan, > > What complexity does signing add, once it has been set up for the project? > By signing a library it becomes easier to use regular releases in more > situations. > > Regards, > Gerke. > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rhino-tools-dev/-/1DcmLKBRzTkJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
