> If the company where you are working can't approve the usage of .NET4
> well... you must be happy with NH3.0.x or you have to find somebody to
> maintain NH3.0 for you.

It's not just the company IT department who needs to approve this. It
involves upgrading build systems, developer tools, etc. Furthermore,
you're also forcing all of your customers to upgrade to .NET4.

I agree that NH should move to .NET4, but if there can be at least
some degree of backwards compatibility with .NET3.5, even at the cost
of a reduced featureset, that would be very beneficial in terms of
getting people to adopt NH, or to keep them using it.

Roy

Reply via email to