Should I pursue ASP.NET WebForms or ASP.NET MVC
Firstly, I'm a software engineer doing web development in ASP.NET. We have a custom framework that we use that sits on top of .NET so most of my development work leverages more of our internal framework and less of the traditional web forms model.

I've done web development for a couple years on my own as well, but I mostly use LAMP (with some work with Ruby on Rails) for these projects; however, I've recently had some opportunities for .NET development. The problem is that most of my ASP.NET experience, as you can see, comes from an internal framework and less from the native controls.

I have no problem getting a book (or three), a few podcasts, and some web sites, and getting down deep in the ASP.NET WebForms; however, with ASP.NET MVC on the horizon and with my experience (and appreciation) for an MVC framework, I feel as if I'm at a crossroad - should I pursue an in-depth understanding of web forms, or do the same for MVC?

I'd like to note that I've read the posts dealing with WebForms vs. MVC, so I'd like to clarify that my question is that I have some concerns for choosing either technology over the other. These are:

  -  How hard would it be going from one to the other, should I need to do so, down the road?
  - I like to typically write my presentation code (XHTML/CSS/JavaScript) by hand with a JavaScript framework and tend to stay away from the code-front controls.
  - Am I shooting myself in the foot (in terms of marketability in the future) if I choose one over the other?

Should I pursue ASP.NET WebForms or ASP.NET MVC
===

Firstly, I'm a software engineer doing web development in ASP.NET. We have a custom framework that we use that sits on top of .NET so most of my development work leverages more of our internal framework and less of the traditional web forms model.

I've done web development for a couple years on my own as well, but I mostly use LAMP (with some work with Ruby on Rails) for these projects; however, I've recently had some opportunities for .NET development. The problem is that most of my ASP.NET experience, as you can see, comes from an internal framework and less from the native controls.

I have no problem getting a book (or three), a few podcasts, and some web sites, and getting down deep in the ASP.NET WebForms; however, with ASP.NET MVC on the horizon and with my experience (and appreciation) for an MVC framework, I feel as if I'm at a crossroad - should I pursue an in-depth understanding of web forms, or do the same for MVC?

I'd like to note that I've read the posts dealing with WebForms vs. MVC, so I'd like to clarify that my question is that I have some concerns for choosing either technology over the other. These are:

  -  How hard would it be going from one to the other, should I need to do so, down the road?
  - I like to typically write my presentation code (XHTML/CSS/JavaScript) by hand with a JavaScript framework and tend to stay away from the code-front controls.
  - Am I shooting myself in the foot (in terms of marketability in the future) if I choose one over the other?
