Thanks for the info. IoC/DI adds a little more complexity than I'd like, but I'm still learning. I just found this book on Unity, and I'm finding it a good resource: http://unity.codeplex.com/documentation

>In MVC, IoC will work for you.
>
>There are people that don't like DI. I believe Rick Strahl has discussed issues with it. You can still do it the same way you are now.
>
>>It's an MVC app, although business logic will be in business objects, so it will be something like MVC -> Business Objects -> Entity Framework. Theoretically, the business object layer will work with any type of .NET front end. My main concern is the ability to put a customized business object in a separate DLL.
>>