[nhusers] Re: NHibernate and .Net 4.0 compatibility issues

2010-05-18 Thread Trinition
We just kicked off a Silverlight 4, WCF, .NET 4 project with NHibernate. We've already passed our first NHibernate calls originating on WCF threads without a problem. On May 17, 9:28 am, Mehran wrote: > Hi all, > We have a project written in Silverlight and WCF. The software is in > two parts :

[nhusers] Re: NHibernate and .Net 4.0 compatibility issues

2010-05-17 Thread Mehran
Thanks Tuna, Oskar is right I did not metioned any details but I just only want to get hints on existing and known compatibility problems. Your hint was very useful. Yes, we have experienced an exception calling old style Assembly.LoadFrom() method. Perhaps re-generating the WCF proxies by using th

Re: [nhusers] Re: NHibernate and .Net 4.0

2010-05-13 Thread Oskar Berggren
I would really like to see a .Net 3.5 version of NH3, to get access to the new LINQ-provider etc. If there are big benefits of having NH compiled for .Net 4, maybe it would be a good strategy to after the release of NH3 for 3.5, then focus on just the minimal changes needed to usefully compile on

[nhusers] Re: NHibernate and .Net 4.0

2010-05-12 Thread Graham Bunce
It would be great, but too soon. Many people want a full Linq provider who are not able to upgrade to .NET 4.0 straight away. IMO on way would be a release of 3.0.0 as .NET 3.5 and an immediate branch to (e.g. 4.0.0) for a .NET 4.0 version. Maintain 3.x in .NET 3.5 as a bug patch version alongside

Re: [nhusers] Re: NHibernate and .Net 4.0

2010-05-10 Thread Mohamed Meligy
Same here, so many ISet errors, wanted to entirely remove the lessi collections assembly even, but there are other classes used from it. For now it's working just fine to use NH from .NET 4.0 projects. I have one main project upgraded recently to .NET 4.0. A Web Application Project, services layer

[nhusers] Re: NHibernate and .Net 4.0

2010-05-10 Thread graphicsxp
Hey Michael, I was wondering if you had made progress on this ? Did you manage to get your project working with .net 4 ? Ta On 5 mai, 08:34, graphicsxp wrote: > Good to hear I'm not the only one having this issue > > I've tried to upgrade NH to .net, but I've given up. I had too many > error

[nhusers] Re: NHibernate and .Net 4.0

2010-05-04 Thread graphicsxp
Good to hear I'm not the only one having this issue I've tried to upgrade NH to .net, but I've given up. I had too many errors, mostly due to the new ISet interface in the .net framework. I believe that all I need is the website to be in .net 4, and I shouldn't have to upgrade the other proje

[nhusers] Re: NHibernate and .Net 4.0

2010-05-04 Thread Michael Hedgpeth
I am having the same issue. All of my assemblies are on .NET 4.0, but are referencing assemblies that are compiled as .NET 2.0 (including NHibernate). The error I'm getting also happens on the BeginTransaction() call. I'm guessing this has something to do with my configuration, so here it is:

[nhusers] Re: NHibernate and .Net 4.0

2010-04-29 Thread graphicsxp
A little bit more information : If I test my DataAccess Layer project using Unit Tests instead of my website, then I get this exception (still when calling BeginTransaction() ): The runtime has encountered a fatal error. The address of the error was at 0x5b425ad7, on thread 0x1064. The error code

[nhusers] Re: NHibernate and .Net 4.0

2010-04-29 Thread graphicsxp
I've checked that, but I'm definitely using the framework 4 and it's not set to ClientProfile. I'm still getting the same runtime exception. Do I need to recompile NH with .net 4 as well ? On 29 avr, 14:46, Gabriel Bogéa Perez wrote: > You may also check if your target framework is not set to .N

[nhusers] Re: NHibernate and .Net 4.0

2010-04-29 Thread Gabriel Bogéa Perez
You may also check if your target framework is not set to .NET 4 Client Profile, if it is try changing it to .NET 4. I got this error when upgrading a project. Gabriel. On Apr 29, 7:19 am, graphicsxp wrote: > Humm...yes, you are right, this error message is obsolete. > > My website is in .net 4.

[nhusers] Re: NHibernate and .Net 4.0

2010-04-29 Thread graphicsxp
Humm...yes, you are right, this error message is obsolete. My website is in .net 4.0, but my DAL project is still in .net 3.5 because I didn't want to fix all the errors related to the new ISet interface being ambitious with the IESI ISet. Maybe I should change that project to use .net 4.0 as well

[nhusers] Re: NHibernate and .NET 4.0

2009-06-24 Thread Tuna Toksoz
The dynamic stuff... as long as you use 4.0 as if it is 3.5 then there definitely isn't any problem. Tuna Toksöz Eternal sunshine of the open source mind. http://devlicio.us/blogs/tuna_toksoz http://tunatoksoz.com http://twitter.com/tehlike On Thu, Jun 25, 2009 at 1:14 AM, Dario Quintana < co

[nhusers] Re: NHibernate and .NET 4.0

2009-06-24 Thread Dario Quintana
Why ? The best way to know it is to run the whole suite of tests against the .Net x. But I think it's the same, and it will work ok. On Mon, Jun 22, 2009 at 6:32 AM, Graham Bunce wrote: > I'm thinking lazy loading not working properly or session > becoming corrupted somehow. Would the code run i