It will require me putting explicit versions when listing the dependencies for a package.
On Tue, Dec 27, 2011 at 12:51 PM, Matt Burton <[email protected]> wrote: > Sounds good for the future plans. Do you happen to know the magic > incantation to get NuGet to behave in this circumstance? Or is this a > manual hack-n-slash affair? > > Thanks for your help, > Matt > > On Dec 27, 2011, at 11:46 AM, Corey Kaylor <[email protected]> wrote: > > I vote for updating to the latest. I think I'm going to change things to > depend on the nuget packages instead of a shared lib. There have been some > improvements in this area that would have been painful for RSB due to > supporting multiple framework version. This should make updating things > much quicker and easier. Likely it will just pull them down rather than > version them. > > In the meantime, if you install the explicit version of log4net that RSB > depends on it should resolve your immediate issues. I know it's a pain > though. > > On Tue, Dec 27, 2011 at 12:10 PM, Matt Burton <[email protected]>wrote: > >> We had a lull in our release cycle and thought I'd upgrade us to the new >> version and I'm having some difficulty, unfortunately. Looks like there's a >> new version of log4net out there (1.2.11) that's causing issues. Since the >> RSB package doesn't specify an exact version of log4net it is automatically >> upgrading that dependency, and that's causing runtime binding issues. I'd >> like to avoid sprinkling binding redirects everywhere - they cause nothing >> but headaches going forward. Also, it looks like the new version of log4net >> is signed differently, which may be causing some of the problems - not >> sure. Would it be possible to update the package so that it specifies the >> exact log4net version or simply upgrade to the latest version of log4net >> altogether? >> >> Or perhaps I need to be schooled in my NuGet-fu, in which case I'm all >> ears... >> >> Thanks, >> Matt >> >> >> -- >> 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/-/Z_loI5Vzez0J. >> 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. > > -- > 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.
