<p>Starting a new project and would like to use one of the MVC framworks.  <a href="http://www.asp.net/mvc/" rel="nofollow noreferrer">ASP.NET MVC</a> is still in preview but <a href="http://springframework.net/" rel="nofollow noreferrer">Spring.net</a> is in production and has a history with Java.  I'd like to know the general lowdown between the two.</p>

<p>Current questions..<br>
What are the major feature differences?<br>
What about deployment/hosting issues?<br>
Future support? Do you think Spring.net will fade once ASP.NET MVC is in production.<br>
Current Support?  I saw the Jeff twitting about a breaking change in the next preview.  </p>

<p>Thanks!</p>

I am a little confused by the question.  Spring.Net is a dependency injection framework that you can use in ASP.NET MVC.  I kind of based my answer off what you are actually asking though.  The difference between ASP.NET MVC and another MVC framework that runs in ASP.NET.
If you are worried about using ASP.NET MVC in production since it is not even in beta yet, then you may want to check out
MonoRail
as an alternate.  There are some differences in features, but the two are pretty close in terminology and how MVC is implemented.  To learn differences,
here is a question
that was posted, that you might want to monitor.  I think once ASP.NET hits release, that most Microsoft shops will switch to it.  With ASP.NET MVC still being developed, you will run into breaking changes that you will have to change when you upgrade to the next release.  That goes with the territory of living on the edge.  You just need to read the release notes before jumping to the latest release.