January 2005 - Posts
The new criteria for evaluating object-relational products for .NET seems to be "Can I install and start using it within 30 minutes?"
And that's a completely reasonable expectation. There is no doubt the technology has matured. But if we ever hope for the adoption rate for OR Mapping to climb we have got to build tools that are easy to install (and use for that matter). How many countless lost souls searching for object-relational deliverence in the barren wilderness that is ADO.NET and DataSets have been thwarted at the last moment before salvation just because they couldn't install the product and start working with it in a reasonable time?
And I must say that Versant is doing their part to advance the state of the art to make object-relational mapping accessible to the masses. Their product is easy to install and has fantastic Visual Studio integration. Check it out for yourself. Heck, it bet you could be using object-relational mapping in 15 minutes!!!
The minutes are counting down: Tick-tock. Tick-tock. Tick...
Two more web seminars are scheduled.
Kicking the DataSet habit: An Introduction to Versant Open Access .NET
February 24
March 10
Click here to enroll
As most of you know, I'm pretty excited about this product. In this seminar I give a background on the motivations for using object-relational mapping then I create a complete - albeit modest - application using the RAD features of Versant Open Access .NET. You can use a domain model to organize your business logic (not DataSets) and you get Rapid Application Development. I call it Uncompromised RAD.
Join me next time and tell your friends.
I like to program with a domain model. So I wanted to showcase the portions of my site built on a domain model by putting them front and center. When I set up my web site I put Cuyahoga as the main portal and made Community Server subservient to Cuyahoga by placing it in a virtual directory.
There was just one glitch. Cuyahoga registers some HttpModules to manage its NHibernate session. Those HttpModules need to be disabled for the Community Server portions of the site. "No problem!" one would think. "Just remove them in the virtual directory's web.config."
Here are the settings that do that.
<httpModules>
<remove name="UrlMandlerModule" />
<remove name="AuthenticationModule" />
<remove name="NHSessionModule" />
</httpModules>
The catch is that you have to copy the DLL for Cuyahoga (Cuyahoga.Web.dll) to the bin directory for Community Server. For some reason ASP.NET has to know about the module before it can remove it! This post helped me find the solution.