title: ASP.Net MVC requirements vs ASP.Net? (hosting question, plus LINQ-to-SQL question)
body: <p>I'm jumping into ASP.Net MVC and wanted to know how tough it's been for hosting providers to support it.</p>
  
  <p>One thing that I'd like to know is how I can port my local MVC app to a hosted provider if I'm using LINQ to SQL.  I assume I have to move the dbml files over in some way?  What else that's special in contrast to a regular ASP.Net app?  (Sorry if this is a complete newbie question, I'm trying to get a feel for the steps involved.)</p>
  
  <p>Can anyone give their opinion on how quickly providers are adding support for ASP.Net MVC?  I'd also like to know if it's going to be a Big Deal and get future support and love from Microsoft or if it's being thought of at Redmond as an experiment compared with webforms, subject to being pulled without notice.  I ask this one because I'm seeing a lot of jobs on the usual boards involving Spring, Hibernate &amp; J2EE, and a comparative lack of ASP.Net (much less ASP.Net MVC) offerings and wonder if this tide will turn at some point.  (Feel free to disagree with me on the number of jobs involving J2EE &amp; LAMP vs ASP.Net, but that's my observation.)</p>