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

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 开发者_Go百科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.

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.

In regards to question 2 I would suggest to be very upfront with them about how soon (if at all) they will be using MVC. I've met a few MVC developers that would hate the idea to go back to WebForms and that has been a deal-breaker for them.

As far as their skills is concerned, MVC developers tend to know (and be comfortable) with raw web development (HTTP/HTML/state-less) and those skills are handy even when you are doing WebForms.

It doesn't sound like you need MVC at all, until you start developing new applications.

Question 1: it would be a very bad idea to redevelop everything. If it ain't broke, don't fix. Unless you want to lose money... or your job.

Question 2: Not unless you need them. Which you don't unless you are developing new apps that would benefit from mvc.

Addendum: There are a few reasons for hiring MVC developers:

a. To future proof your business. The day may come when you need those skills in your team. However, it might be cheaper to head hunt as the need arises. Or else boost the morale of your team by offering the opportunity to train in MVC whilst they mentor a junior web form developer.

b. To future proof your CV. If you have led a team of MVC developers, your job prospects will brighten. However, if your boss loses money you will get the sack and that will be on the record.

c. You can mix and match MVC with plain vanilla ASP.NET. So as new requirements come up in your app, you can build them in MVC. However, what will the morale be in your core team if the new boys get all the fun stuff and they get the dross?