I got my only experience with .Net technology three years ago when I led an implementation of an in-house persistence framework. We ported a J2EE framework with well known patterns to .Net and created two frameworks that are consistent and are used by both camps, Java and Microsoft, within our company.

That J2EE framework also had a presentation layer framework based on Java Server Faces (JSF). Obviously, for our .Net project we could not port that part and went for standard ASP.Net implementations. Needless to say, I was never comfortable with this technology since I did not grow up with it. Standard ASP.Net needs a total shift in thinking and on top I never was convinced that ASP.Net was meant for the HTTP protocol; it always felt like a fat client technology stuffed into a HTTP box.

While looking for alternatives for our persistence framework, I came across articles of ADO.NET Entity Framework (EF) and soon had my first examples running. Naturally, I added the ADO.NET Data Services layer on top of EF and had a RESTful interface to my data in no time.

Then there was the question of what UI layer to use; maybe I could use Silverlight or would I really have to dig into standard ASP.Net? Fortunately, I found articles about ASP.NET MVC and was surprised and excited at the same time. ASP.NET MVC is nothing else then JSF on steroids. I have written several code generation projects for JSF and seeing now that Microsoft has adopted this technology made my choice obvious.

This whole blog is dedicated first to explore ASP.NET MVC. I am looking forward to see your comments on this site!