I have also made some minor testing for .net 4, just for kicks.

Just getting it to compile is easy, just prepend all ISet declarations with
the full Iesi namespace and you're done. I cant get the tests to run atm
though, i tried to rebuild nunit for .net 4 but I get an assembly load
exception when trying to load NHibernate.Test.

Some of the dependencies probably needs upgrading too. The Castle team seems
to plan to support .net 4 pretty soon but I haven't managed to compile
Castle.Core (incl DP) yet.

Regards,
Johannes

On Fri, Apr 16, 2010 at 2:51 PM, Jon Palmer <
[email protected]> wrote:

> Fabio,
>
> I know that .net 4.0 has only been out for a few days but there have
> been betas and rc before that. Has anyone done any experiments around
> this issue? I notice that Oren has had some thoughts around this
> problem back in April last year:
>
>
> http://ayende.com/Blog/archive/2009/04/23/nhibernate-tidbit-ndash-using-ltsetgt-without-referencing-iesi.collections.aspx
>
> We (and I'm sure many others) are pretty aggressive about
> upgrading .net versions. It would be a shame if NHibernate support
> significantly slows down that process. Is there a roadmap that would
> help us understand the rough timing that support is planned for
> (quarter of the year would be fine) so we can start to plan that into
> our development/release strategy? In particular do you think it is
> likely that there would be a minor point release that adds .net 4.0
> support or is it more likely that we have to wait for NHibernate 3.0?
> Lastly is there work that we can help with to add .net 4.0 support?
>
> Thanks
> Jon
>
> On Apr 15, 11:55 pm, Fabio Maulo <[email protected]> wrote:
> > wait... wait... take it easy.
> >
> > On Thu, Apr 15, 2010 at 10:43 PM, Jon Palmer <
> >
> >
> >
> >
> >
> > [email protected]> wrote:
> > > NHibernate Dev,
> >
> > > Has there been any thought about how how NHibernate will support .net
> > > 4.0? After attempting a quick port of our code base to .net 4.0 we're
> > > seeing a number of issues mostly around ambiguous match exceptions
> > > that seem to stem from the newly introduced ISet<T> and the Iesi
> > > interface of the same name.
> >
> > > I'm sure its a non trivial problem to resolve but it would be useful
> > > to understand what the plan might be.
> >
> > > Thanks
> > > Jon
> >
> > > --
> > > Subscription settings:
> > >http://groups.google.com/group/nhibernate-development/subscribe?hl=en
> >
> > --
> > Fabio Maulo
>

Reply via email to