Microsoft MVC or Is the Monorail off it's track?

For those of you who didn't know, Microsoft has been working on it's own MVC framework. I haven't used it yet since I am in the middle of testing several Web-testing tools for an upcoming article. That said, I have done a little research on the web and here are a few things that Monorail users may want to know:

• Hammett, the founder of Castle::Monorail, has helped MS by making suggestions about their implementation. See his comment below:
  

  I'm not actively collaborating with MS regarding the MS MVC. I've offered help due to my expertise with complex web sites we have built using MonoRail, I was invited to fly to Redmond and analyze their product, and discuss things, make suggestions.

• It's been suggested (in comments) that Monorail may become a wrapper for the MS Framework, if the MS MVC framework progresses well.
• The MS Framework does support intellisense in it's views. Views are written in your .Net language of choice.
  
• ASP.Net controls are available for use in Views.
  
• The MS Framework does not forbid the use of ActiveRecord but with LINQ on the horizon developers may choose it. (I haven't played with the LINQ extensions yet)
  
• Monorail is more time tested (and just works)! Also, the MS framework is closed source.
• The MS MVC framework will allow you to use any xUnit framework and any Mocking framework you choose but, as of this writing the MS solution has nothing nearly as kewl as the Monorail BaseControllerTest.
• I can find nothing about IoC support in the MS offering.
• Some people believe the routing engine in the MS offering is easier to configure. I'll have to test this assumption.

I personally have no plan to switch to the Microsoft framework yet. I DO believe the MS Framework will introduce MS developers to how great MVC can be. I also believe that Microsoft will slowly position the MVC framework as it's preferred web-app architecture. The ASP.Net architecture, while successful, was a fundamentally flawed offering that should be abandoned quickly.

As Microsoft moves into this new territory we'll start to see a subtle change in how they do business. The .Net framework was their last major move ( just had it's 6 year anniversary). The latest signs of change are already out there; LINQ, extension methods, the MVC architecture. Things to look for now; Redesigning the Ajax.Net library, functional programming with F#, greater support for DSLs.

Some Interesting Links

• Code Rant: Writing Unit Tests with the MVC Framework
• Hammett's article about his visit to MS.
• Oren discusses protected methods in the MS MVC.
• Oren discusses the ControllerActionAtribute. This has alreay been removed by MS...
• Ryan doom asks which Framework to Go with...
• The Castle::Monorail site.
  

Let me know if you have any other questions. I'll try to answer them as I play with the new framework.