MS just released ASP.NET MVC RC2 yesterday which requires .NET 3.5 SP1. I can now see a dependency between the two. This stuff is still not entirely stable yet. This is in contrast to how Java MVC frameworks are not necessarily dependent on JDK updates. So it appears that ASP.NET MVC and the .NET 3.5 framework are co-dependent. This is not a good thing for stability and is bit on the accidental-edge. From where I sit, it looks like MS is back to its usual tactics with using the underlying framework (or OS, or API, or whatever) to remain in the drivers seat. It looks like ASP.NET MVC is driving the change to the .NET 3.5 framework.
Note: .NET 3.5 was released in Nov2007. .NET 3.5 SP1 was released in Nov2008.
The Microsoft Entity Framework, aka ADO.NET Entity Framework, implements the Model aspect of ASP.NET MVC and is tightly coupled to .NET 3.5 SP1. Based on a few blogs, it appears that MS is having problems with their MVC implementation “Testers give Microsoft’s Entity Framework a no-confidence vote” as late as June 2008. Here we are in March 2009 after 9-months and it is still an evolving work in progress.
In contrast, MVC webapp frameworks in Java (since 2000) and many Web2.0 languages (PHP, Ruby) have been around for years.
ASP.NET MVC is still trying to get out of the gates. Looks like Microsoft came to MVC party after the cleanup was done. At least they showed up. I recall looking for MVC webapp frameworks for .NET back in 2005-2006 and found nothing at the time.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment