On Tue, Nov 23, 2010 at 11:00 AM, David Pfeffer <[email protected]> wrote:
> Personally, if NH3 is released without the issues with the LINQ provider > working, I'm going to have to keep my project using the trunk so that I can > get at the LINQ bug fixes. Right now I have HQL scattered throughout my > project, and I really want to replace all of the queries with LINQ so that I > can reduce coupling to NHibernate. I'm sure many other people would follow > suit. > LOL. The repository pattern is for something. string SQL spanned everywhere, HQL spanned everywhere or LINQ-to-DB spanned everywhere make no difference. before IL compilation a LINQ sentence is a string as before NH compilation (BuildSessionFactory) a HQL is a simple string. > > I'm not saying its necessarily a negative that I and others might not be > able to use the release version of NH, but you have to decide if its > important to you that people be able to use your release product. Right now > from talking to my friends in the developer community, nearly all of them > think NH has a reputation that "you always have to use the trunk." what ? The trunk is only for one thousand of pioneers. -- Fabio Maulo
