I am getting a lot of mileage out of Pluralsight. Thanks again for that tip. Now that the price has dropped to $39/month (first month free) it's affordable.

Dependency injection with MVC was John Petersen's exact topic on Saturday. It was an excellent presentation, although of course you're not going to learn everything about it in 80 minutes.

>There are a couple hours on ASP .NET with MVC on Pluralsight.
>
>Be sure you also know about Dependency Injection, IOC, and at least know what Unity and MEF are.
>
>>>>>>Seems like a great idea. I'm not a MS hater by any means, but it seems that when a third party has the benefit of hindsight they can hammer out a great product.
>>>>>>
>>>>>>>I haven't used it. Hadn't even heard of it until recently. We had two presentations on it at Utah Code Camp this past weekend, one of them by one of the guys behind Fubu. Unfortunately, I couldn't get to either of them.
>>>>>>>
>>>>>>>>Ah, I forgot about MVP. Never got into that much as I am headed in the MVC direction. Have you used FubuMVC?
>>>>>
>>>>>Congrats on the new job. Is it more or less of a commute?
>>>>>
>>>>>The floor is still open on MVC vs. MVVM....
>>>>
>>>>How can you say that? Just because you have a couple of months knowledge in .Net doesn't make you an expert, neither does my 9 years, but I am adaptable to what works and what works well. We have been using MVVM for nearly 2 years now. The power of Silverlight and WPF is in its capability to bind to data easily. The power of MVVM is in the binding of the ViewModel to the View... Binding is the key.... It all happens auto-magically when set up correctly.. MVVM works extremely well with silverlight, MVC not so well.
>>>>
>>>>P.S.
>>>>
>>>>One of the other things is the ability to bind button click events directly to a property in the view model.
>>>
>>>Personally, for WPF I prefer MVVM and for winforms, MVP...
>>
>>What about ASP.NET? MVC?
>>
>>Our old pal John Petersen spoke on MVC at the conference I attended on Saturday. (Being slightly facetious there. I know some here will never forgive him. FWIW he was OK to chat with for a few minutes and definitely knows ASP.NET inside and out). One thing I wanted to come away knowing was the difference between MVC 3 and MVC 2. My impression was not that much. Here are the points I noted::
>>
>>1. In MVC 3 you don't have to create your own factory pattern in the main module.
>>2. It handles IOCContainters (inversion of control) for you.
>>3. Remote validation.
>>
>>I should definitely attend more events of this sort. I'm already signed up for a Code Camp here on May 14.