Nhiberbnate and asp.net
it might be an implementation question, but i didn't get reply on the .net forum so i thought that you can guide me. i started reading about it and want some advice/best practices with regards to asp.net development i also read this article which looks quite interesting but to complex for begginers. here is the summary of the article: * Business objects should communicate with data access objects via interfaces; i.e., always depend on abstractions. * Concrete data access objects should implement interfaces defined by the "client", the business logic layer. * Expose data access objects via an abstract factory to assist with testing and to reduce coupling. * Keep NHibernate session management details out of the presentation and business logic layers. * Use unit test categories to easily turn off unit tests that depend on a database connection. * Set hibernate.default_schema within web.config to give NHibernate a great performance boost! here are my questions: 1. is it true that the idea behaind Nhibernate is to create the DAL for me so my app will look like this: GUI->BL->DAL (created by Nhibernate) ? 2. if i have some reports in my app that are gathered from many tables in the DB, can Nhibernate handle this?