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 On Sun, May 22, 2011 at 6:49 PM, David Rolland <[email protected]> wrote: > 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 > > On May 23, 1:03 am, Nathan Palmer <[email protected]> wrote: > > 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 > > -- > 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.
