I appears that some (if not quite all) of these issues are addressed in a later release of the reLINQ provider (atop which much of NH's LINQ support is based). We are looking into this and if it proves to be the case its likely that NH 3.0.1 would probably include these updates, addressing most of these VB.NET-related issues.
In the mean time, if you want to expedite this process for your own consumption, you can build the NH3 release code against the absolute latest trunk build of reLINQ and see for yourself if this addresses these issues. (BTW, if you do pursue this then it would be beneficial if you report your results back to this thread). Regards, -Steve B. On Dec 6, 10:41 am, JamesSpibey <[email protected]> wrote: > Hi, > > I've just download NHibernate 3 GA and was disappointed to find that > the new NHibernate Linq provider has the same problems with VB.NET > that the previous on did, mainly > > - Handling of Nullable types (Neither IsNothing(x) or x.HasValue) work > - Equality operator on strings (although we can get around this by > using the Equals() method) > > Moving to C# is not an option for us. Are there any plans to make the > linq provider work with VB.NET? -- 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.
