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 version 4.x but develop the next proper version of NH from version 4.x onwards, in .NET 4.0. A bit more work but if there are performance/technical issues with NH running under 3.5 but being used by 4.0 (and I don't know if there are) then it's the only way forward that lets .NET 3.5 developers use the new Linq provider and other features. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
