Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80225 --- shadow/80225 2006-12-11 17:58:30.000000000 -0500 +++ shadow/80225.tmp.4166 2006-12-12 05:43:34.000000000 -0500 @@ -81,6 +81,12 @@ While it has nothing to do with Mono fixing the issue, I still think you should report the issue to NHibernate folks. Why ? because it's the "right thing" to do when you find a bug. It's also a simple change (for them), it may fix an issue for NHibernate (e.g. if MS does returns null in certain cases) and it also allows existing versions of Mono to execute NHibernate. + +------- Additional Comments From [EMAIL PROTECTED] 2006-12-12 05:43 ------- +Ok, I see. However, I have tried with the 1.1 profile in MS and it +always returns not null for me too. + +I will attach a simple testcase. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
