James has posted on nhusers, I took it here. If he tries, it should resolve the problems with VB-specific string comparisons. Null handling needs to be supported by code in NH.
(That said, we probably could include support for the VB runtime's IsNoting method (convert to == null). This is a very strange VB feature, nobody bothered to ask about that until now.) BTW, note that there are at least two open re-linq issues that would solve requests on nhusers: https://www.re-motion.org/jira/browse/RM-3474 https://www.re-motion.org/jira/browse/RM-3551 Stefan ________________________________ From: [email protected] [[email protected]] on behalf of Stephen Bohlen [[email protected]] Sent: Tuesday, December 07, 2010 15:28 To: nhibernate-development Subject: Re: [nhibernate-development] Fwd: NHibernate 3 GA, Linq and VB.NET James, would you be willing to make this change and report your results to the dev list so that we could validate that this approach will address your reported issue(s)? Steve Bohlen [email protected]<mailto:[email protected]> http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Tue, Dec 7, 2010 at 8:59 AM, Stefan Wenig <[email protected]<mailto:[email protected]>> wrote: I'm not sure what bugs exactly James is refering to, but I just realized that NH 3.0 GA was released with re-linq 1.13.41, from March. VB support was included in 1.13.68, currently we're at 1.13.85. I recommend you update, test, and release a hotfix release for VB users if you want to support VB. HTH, Stefan ---------- Forwarded message ---------- From: JamesSpibey <[email protected]<mailto:[email protected]>> Date: 6 Dez., 16:41 Subject: NHibernate 3 GA, Linq and VB.NET<http://VB.NET> To: nhusers 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<http://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<http://VB.NET>?
