To me the most important aspect of the new release is the LINQ provider rewrite.
LINQ is now a non-negotiable part of programming in .NET. LINQ support is the weakest point of NHibernate, and it detracts from its otherwise awesome qualities. Current NHContrib version of the LINQ provider is broken in many fundamental areas - grouping, joining, comparison e.t.c. Using either HQL or criteria API to plug those areas results in inconsistent bulky codebase that is hard to maintain. I can't in all conscience use the trunk, as Fabio suggests. Tried it before. For all the assurance that nothing gets contributed to the trunk if it fails a test, the reality of the situation is, effective full coverage unit tests can only be produced from sufficient exposure to real life production environments, and that just doesn't happen until the software is officially released. Especially with the LINQ provider, for every 1 problem solved 1 problem that was solved before is now broken, so I would much rather wait. At least I KNOW what's broken in the 2.1 LINQ provider now so that I can avoid it. -- 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.
