Signing an unsigned assembly

Posted by dagda1 on Stack Overflow See other posts from Stack Overflow or by dagda1
Published on 2009-11-03T18:12:01Z Indexed on 2012/08/28 9:38 UTC
Read the original article Hit count: 342

Filed under:
|

The recent upgrade of NHibernate 2.1 has brought a mega headache situation to the surface.

It seems most of the projects build by default as signed assemblies. For example fluentnhibernate references the keyfile fluent.snk.

Nhibernate.search builds unsigned from what I can gather and will not build signed that is if you reference a generated keyfile, you get the error:

Referenced assembly 'Lucene.Net' does not have a strong name

This means projects like castle.activerecord that have nhibernate.search as a dependency will not build as you get the horrendous error referenced assembly nhibernate.search does not have a strong name:

Quite a few projects use caslte.activerecord so it is quite important that this builds.

Has anyone any idea what to do here as I am totally out of ideas?

This is complete madness.

© Stack Overflow or respective owner

Related posts about .NET

Related posts about horn