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 <[email protected]> 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 [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.
