This release is very solid... We're covering this in detail. This is no add, but to say what domain.dot.net is about : We cover the news in large-scale, software engineering focused domains using C# 3.0/.NET 3.0. This includes Linq, Domain-Driven mastery, Agile is assumed, design pattern mastery etc.

We write in a manner that references advances concepts like the most productive teams communicate (providing the best resource links so catch up if needed).

We also provide APPLICATIONS that USE THE TECHNOLOGY along side the write up of the item, how it fits into the big picture and FULLY FREE AND USABLE CODE.

In short, there is nothing like it, and as this is not sales. I'll shut up now.

Damon Wilder Carr,, CTO
the domain.dot.net team (soon to launch more formally)

What's with all the capital letters? I really don't understand this post or the significance of it. Why all the shouting? Is somebody desperate here?

Ok I read the background. But seriously if you want anybody to take NHibernate seriously then don't be some desperate to release things and announce in big capital letters.

I'm a big fan of NHibernate but unfortunately I can't get it integrated here into my company because I get the following criticism from my co-workers:

1) NHibernate's query language is too complex and we don't have the time to learn it.
2) The documentation is pitiful at best.
3) We have too tightly integrated business logic in POCO's and rewriting it in NHibernate will cost too much time and our client doesn't understand why he has to pay for the rewrite.
4) It's not "Microsoft Standard" (I hate that excuse) and we don't use "Open Sauce"

Getting desperate and CAPTALIZING stuff will definitely not get sceptics on board.

Just my 2 cents.

M

My reason for placing certain items in caps is not desperation in the least. If anything it is the opposite: Most can only scan a post, not read it in detail, so I want to make those points stand out. Also. it is enthusiasm about the state of our industry in the lines of: 'I LOVE THIS JOB'. I can see you do not share this feeling, and who can blame you as your trying to work within a broken culture it would appear.

Your bullet list is based on one this 'incorrect perception'. If you'd like to correct that I can assure you:

(1) and (2) --> Is Linq to complex? Would you consider books on the market covering NHIbernate and Hibernate 'pitiful'? These are not logical statements, they are emotional.

(3) and (4) --> These are 'political/organizational' limitations and any organization that arbitrarily decides to limit their solution set of best case approaches with 'no open source policies' (as we discuss) as fundamentally broken. As for integration in your POCOS that is very common and very fixable, most commonly with a refactoring out of DAO concerns into single responsibility classes which are typically then injected in as services to entities based on a shared interface contract. This is easy, not my idea, and has been standard for years and years. It's basically the strategy pattern however we also strongly recommend using a dependency injection framework and the concepts of inversion of control to fix this issue.

Your post very nicely represent a large group in the .NET community. Until these irrational and illogical beliefs are overcome, that segment will stagnate.

Kind Regards,
Damon Wilder Carr