What can I do in the future to help ensure I dont introduce this kind of 
regression?

On Thursday, February 2, 2017 at 9:05:41 AM UTC-5, Dan Plaskon wrote:
>
> Thanks!
>
> On Wednesday, February 1, 2017 at 8:00:59 PM UTC-5, Alexander Zaytsev 
> wrote:
>>
>> NHibernate 4.1.1 is now released. 
>>
>> For a list of resolved issues, see the release notes:
>>
>> https://github.com/nhibernate/nhibernate-core/blob/4.1.1.GA/releasenotes.txt
>>
>> Binaries are available on NuGet and SourceForge:
>> https://sourceforge.net/projects/nhibernate/files/NHibernate/4.1.1.GA/
>> https://www.nuget.org/packages/NHibernate/4.1.1.4000
>>
>> ##### Notes #####
>>
>> The [NH-3904] has been reverted in favor of [NH-2401]: users now required 
>> to explicitly specify custom user type via MappedAs method if they want to 
>> use IUserType/ICompositeUserType type parameters in Linq queries, or 
>> implement generators the way they take the types into account.
>>
>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"nhibernate-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to