you can re-compile the old provider with NH3.0 and then you can use both together (if you need)
On Thu, Feb 3, 2011 at 8:01 AM, hoghweed <[email protected]> wrote: > HI, > recently I'm doing a port of a big project to the new NH3 from the > last rel. > everything seems work fine, but the "big issue", the "big problem" is > on the new Linq provider. > It's possible the new linq provider supports less features than the > older? > > I was searching on this group about linq issues and fixes to try to > apply, but I saw that there are a lot of unsupported features, so it > could not be better to organize a post or something similar somewhere > which can describe any unsupported feature and the fix to apply. > > Unfortunately, for the breaking changes about the linq provider I have > to backport the solution to NH2.1 > Anyone can help me in finding issues and fixes? > > I hope the answer wouldn't be a 3 line bla bla bla, this question > would be a conversation on that because I see this is a problem many > developers are falling in. > cheers > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- Fabio Maulo -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
