How much to dump on them...

So here's the situation...

We're redesigning the the client's application, piece by piece. Due to the amount of data they need to process, and how they process it, there will be a lot of code in the stored procedures.

Not a problem, we have a dba from my company on the job and he's doing great.

But... the application is currently in classic ASP. The team has mixed experience (e.g. two 20 somethings who's major OO experience is from college. They're willing to learn, just not there yet. Add to that one 60 something who's way behind tech wise... adds up to an immature team.)_

So part one, is introducing them to some basic processes like source code control, versioning and deployment.

Part two, as it were, is diving into major OO concepts. This app looks like it's a good candidate to use MS's new MVC framework for ASP .Net

Finally because of the sophisticated SQL backend this app also looks ripe to use LINQ to get data in and out with minimum fuss.

The issue? How much and how fast can I dump new concepts on the team. I'm worried about absorption rate of the materials (add to this the C# .Net training the will be getting by March 1.) They'r new to ASP .Net and add to that a ORM and MVC framework... could be a bit much (along with process and TDD).

I'm going to prototype as much as possible, I'm just worried they might have some problems siwmming as it were (well... the 20 somethings might do fine. But the 60 something is another issue..)