I looked into assembly binding redirection, but it didnt' work because the Antlr3.Runtime versions I'm working with seem to have different public keys (I think... not sure). I'll ponder whether I want o have to compile my own version of NHibernate against the newer Antlr3.Runtime.
Thanks! Regards, Brian. On Aug 19, 12:08 pm, Tuna Toksoz <tehl...@gmail.com> wrote: > if there are breaking changes, you can use assembly redirection, if there is > no breaking change, compile one against other's antlr dll > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksozhttp://tunatoksoz.comhttp://twitter.com/tehlike > > > > On Tue, Aug 18, 2009 at 5:49 PM, Trinition <trinit...@gmail.com> wrote: > > > I've been successfully using NHibernate 2.1 in my project for several > > weeks. Now I'm adding StringTemplate 3.2 into the mix. Both NHibernate > > 2.1 and StringTemplate 3.2 depend upon Antlr3.Runtime, but apparently > > they depend upon differing versions. NHibernate 2.1 comes with > > Antlr3.Runtime version 3.1.0.39271 while StringTemplate 3.2 comes with > > Antlr3.Runtime version 3.1.3.6002. I can't seem to get my application > > to satisfy both NHibernate's and StringTemplate's dependencies. Is > > there a good way of solving this problem? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhusers@googlegroups.com To unsubscribe from this group, send email to nhusers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
