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 On May 22, 2011, at 2:48 AM, David Rolland <[email protected]> wrote: 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 -- 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. -- 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.
