If you want use ISet<T> of .NET4 you don't need to recompile NH what you
need is just a specific collection factory and more... you don't need to
implement it because it is already available in nuget
http://nuget.org/packages/NHibernate.SetForNet4

On Thu, Dec 15, 2011 at 7:04 PM, Ramon Smits <[email protected]> wrote:

> Me to. Why would you recompile for .net 4? Only needed when you want to
> use .net 4 ISet interface for some situations but in most ICollection will
> be enough.
> On Dec 15, 2011 10:58 PM, "Fabio Maulo" <[email protected]> wrote:
>
>> I'm using NH3.2.0 official release.
>>
>> On Thu, Dec 15, 2011 at 4:27 PM, DBLWizard <[email protected]> wrote:
>>
>>> Where are you getting the source from or where are you putting it?
>>> Right now I have to go through about 50 files and removed the
>>> reference to Iesi.Collections.Generic and Iesi.Collections and then
>>> change all the ISet and HashedSet references to be fully qualified.
>>> The I have to through and add several [SecurityCritical] attributes to
>>> calls like GetObjectData.  These security issues don't show up until
>>> runtime.
>>>
>>> dbl
>>>
>>> On Dec 15, 12:00 pm, Fabio Maulo <[email protected]> wrote:
>>> > I'm using NH3.2.0 in a .NET4 application (all assembly have .NET4
>>> target)
>>> > without problems.
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Thu, Dec 15, 2011 at 1:52 PM, DBLWizard <[email protected]>
>>> wrote:
>>> > > Yeah,
>>> >
>>> > > I've done that .. just trying to keep from having to merge those
>>> > > changes with the updates as the occur.  There were some bug fixes
>>> that
>>> > > have been updated and I either have to go through and redo all the
>>> > > ISet and I think HashedSet and maybe one other collections that have
>>> > > to be changed.  As well as the Security Attributes that have to be
>>> > > added to the GetObjectData and other calls so that they are
>>> compatibly
>>> > > with the 4.0 framework.
>>> >
>>> > > I had just seen some threads that indicated there were two different
>>> > > trees and wanted to make sure I wasn't doing additional work I didn't
>>> > > need to.
>>> >
>>> > > Thanks
>>> >
>>> > > dbl
>>> >
>>> > > On Dec 15, 9:37 am, Stephen Bohlen <[email protected]> wrote:
>>> > > > There is not presently any separate NH source for .net 4.0.  The
>>> present
>>> > > > source tree targets .net 3.5.
>>> >
>>> > > > Although I've not tried, I don't see any compelling reason that the
>>> > > source
>>> > > > would need to change for .net 4.0 compilation *except* places
>>> where the
>>> > > > IESI collections ISet interface will collide with the same
>>> introduced in
>>> > > > the .net 4.0 BCL.  These can be mitigated by some simple namespace
>>> > > aliasing
>>> > > > + fully-qualifying references to ISet in the codebase.
>>> >
>>> > > > -Steve B.
>>> > > > On Dec 15, 2011 11:26 AM, "DBLWizard" <[email protected]>
>>> wrote:
>>> >
>>> > > > > Howdy,
>>> >
>>> > > > > I'm wondering where I can get .net 4.0 version of NHibernate?  I
>>> read
>>> > > > > some posts that refer to having both a 3.5 version and a 4.0
>>> version
>>> > > > > but I can't seem to find where the source for the 4.0 runtime
>>> is.  Can
>>> > > > > somebody clarify this for me?
>>> >
>>> > > > > Thanks
>>> >
>>> > > > > dbl
>>> >
>>> > --
>>> > Fabio Maulo
>>>
>>
>>
>>
>> --
>> Fabio Maulo
>>
>>


-- 
Fabio Maulo

Reply via email to