Is it wise to mix ASP.Net MVC development and ASP.net web form development in the same group of products?

Question

We have a largely asp.net web form team (With some Oracle developers thrown in).

Question 1: Is it a good idea to start using asp.net MVC which will mean redevelopment of a number of standard controls for not much benefit.

Question 2: Is it a good idea to hire developers where there most recent skills are with asp.net MVC?

What are your thoughts on this?

Addendum, edit, etc: I doubt there is any benefit adopting MVC now, given the 100+ applications in this suite of products, and the maintenance/rework this will cause. Given this, is there any particular reason to hire MVC developers, as they won't be hitting the ground running, which is what I need now.

Answer 1

Question 1: If you get no benefit from it, is it ever worth it? Why do you want to rewrite it if it's working? Are you having a hard time with unit testing your web form app? If so, then maybe MVC is the way to go. But if this is a mission critical application than rewriting it for just the sake of rewriting it seems kind of counter intuitive.

Question2: If you need MVC programmers then sure it's a good idea. However, your hiring decision should be based on their knowledge of programming in general, not on whatever flavor of the week development framework they know.