Signing nightmares - HORN Development | Google Groups

link -> Signing nightmares - HORN Development | Google Groups

I found this horrible hack on the web:

Solution of the assigning the strong name to the third part DLL by using
following command on visual studio command prompt.

E.g. Lets say the name of the third party DLL is myTest.dll.
Step 1: Dis-assemble the assembly
        ildasm myTest.dll /out:myTest.il

Step 2: Re-Assemble using your strong-name key
        ilasm myTest.il /res:myTest.res /dll /key:myTest.snk
/out:myTestSN.dll

This code work perfectly to assign strong name.

for verification you can use following command,
sn -vf myTestSN.dll
I was able to patch the lucene.net into the build and nhibernate.search and
more importantly castle.activerecord build now.

This is a short term and horrible hack.  If anyone fancies mentioning the
signing capability to nhibernate then I would be grateful.

Cheers

Paul Cowan

Hack for the signing problem?

I found this horrible hack on the web:

Solution of the assigning the strong name to the third part DLL by using
following command on visual studio command prompt.

E.g. Lets say the name of the third party DLL is myTest.dll.
Step 1: Dis-assemble the assembly
ildasm myTest.dll /out:myTest.il

Step 2: Re-Assemble using your strong-name key
ilasm myTest.il /res:myTest.res /dll /key:myTest.snk
/out:myTestSN.dll

This code work perfectly to assign strong name.

for verification you can use following command,
sn -vf myTestSN.dll
I was able to patch the lucene.net into the build and nhibernate.search and
more importantly castle.activerecord build now.

This is a short term and horrible hack. If anyone fancies mentioning the
signing capability to nhibernate then I would be grateful.

Cheers

Paul Cowan