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 mehran.tah...@gmail.com wrote:
Hi all,
We have a project written in Silverlight and WCF. The
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
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
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
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 graphic...@googlemail.com 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.
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
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
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:
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
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 graphic...@googlemail.com wrote:
Humm...yes, you are right, this error message is obsolete.
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 bogeape...@gmail.com wrote:
You may also check if your target
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
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 grahambu...@hotmail.comwrote:
I'm thinking lazy loading not working properly or session
becoming corrupted
13 matches
Mail list logo
