Strong name signing for Rhino ETL

[David Rolland]

I'm currently integrating RhinoETL in my personal project but I get a compiler error because the Rhino.Etl.Core.dll is not signed with a strong name. I saw the file ayende-open-source.snk but it's not used by the project file.  

Is there any reason that the assemblies are not signed with a strong name ?

[Miles Waller]

Hi,

 

When assemblies are strong-named, then all their dependencies have to be strong-named too.  So I'd hazard a guess that some of the other libraries are not strong-named, though I haven't checked.

 

There's a tool on codeplex called signer which you can use to sign assemblies after compilation and without the source, I used it to get some dependencies past click-once.  It's pretty old - the source doesn't work but the compiled download does: if you have reflector you can decompile it and get a working version or contact me direct and I'll send you a zip.

 

Miles

On Wed, May 18, 2011 at 11:46 PM, David Rolland <rold...@gmail.com> wrote:

I'm currently integrating RhinoETL in my personal project but I get a compiler error because the Rhino.Etl.Core.dll is not signed with a strong name. I saw the file ayende-open-source.snk but it's not used by the project file.  

Is there any reason that the assemblies are not signed with a strong name ?

--
You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group.
To post to this group, send email to rhino-t...@googlegroups.com.
To unsubscribe from this group, send email to rhino-tools-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.

[David Rolland]

Thanks a lot for your answer Miles. It led me to find these other solutions:

1- http://as.codeplex.com/

2- http://stackoverflow.com/questions/1220519/how-to-sign-a-net-assembly-dll-file-with-a-strong-name

I chose the second solution as it only requires to setup a batch file.

It would be a good idea that the automatic builds for RhinoETL create two sets of DLLs, one signed and one unsigned. Do you know to whom I can send this request ?

David

[Nathan Palmer]

David,

I'm the current maintainer of rhino etl. The problem with signing the assemblies is it causes issues for those who don't want signing and providing both adds complexity to the release. Have you pulled down the source and compiled it with the key to resolve your immediate need?

Nathan

--

[David Rolland]

Hello Nathan,

The first thing I tried was to modify Rhino.Etl.Core.csproj to include
the strong name signing. This worked but it is not a viable solution
for me as I would have to fetch the source code and rebuild the DLL
after each release.
Now using a batch file to disassemble and reassemble the dll using a
strong name is not the perfect solution but it is satisfying for my
needs.
If, as you say, providing both sets of dll (signed/unsigned) adds too
much complexity then it's okay I can live with the batch file
solution.

Thanks for your support,

David

[Nathan Palmer]

I'm glad you were able to get it worked out by recompiling. I understand the worries about having to recompile after every release. It's not necessarily difficult to have it build a signed version at the same time. What I worry more about is the complexity of having two releases published along with publishing a signed version to nuget with references to other signed assemblies. 

Nathan Palmer

[Gerke Geurts]

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.

[Nathan Palmer]

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

--

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.