March 2006 Entries
On a previous post, I mentioned my introduction to Model-View-Presenter (MVP). I've now gotten a chance to try it out on a new project and have been very pleased with the results thus far. MVP provides an approach for clean separation of concerns within the ASP.NET presentation layer without dismissing the page event model. MVP sees the code-behind, along with the ASPX page, as strictly part of the view and provides a patter to treat it accordingly. Although the pattern itself is easy to understand...
Arguments abound for whether or not ASP.NET provides adequate MVC. On the other hand, many feel Page Controller and Front Controller are the way to go. Others feel the entire page model should be abandoned in the favor of something more attuned to Ruby on Rails such as Castle MonoRail. For me, I've always liked the page event model and feel user and server controls are wonderful, but have struggled with making the code behind strictly part of the view. I believe Model-View-Presenter is the answer....
I finally got around to it... the whole shebang of NHibernate best practices with ASP.NET and Generics. The article, along with the related source, can be found at http://www.codeproject.com/... Your review, feedback and suggestions would be much appreciated! 3/3/06 UPDATE I've updated the article on Code Project to include a unit testing project to show how to simulate the web context and how to create “mock” DAO objects within your unit tests...
When NHibernate prepares SQL queries for SQL Server, it passes them to sp_execsql. Upon first call, the query speed is lackluster as it parses and executes the SQL; on subsequent calls with the same query syntax, the speed gets a bit faster. But even on subsequent calls, the response time is much slower than that of a stored procedure. The problem is, by default, NHibernate does not fully qualify table names within its queries sent to SQL Server. To leverage sp_execsql to its fullest, requests must...