I have just migrated my EFMVC app from ASP.NET MVC 4 Beta to ASP.NET MVC 4 RC. In this release, the EFMVC solution is built with Visual Studio 2012. The migration process was very smooth and did not made any major changes other than adding AutoMapper for mapping between View Model objects and Domain Model objects.
The following changes has been made in the current version
- Migrated the app to Visual Studio 2012 RC and ASP.NET MVC 4 RC
- Autofac.Mvc4 package migrated to Autofac ASP.NET MVC4 (RC) Integration
- Autofac.WebApi package migrated to Autofac ASP.NET MVC4 (RC) Integration
- The Windows Azure Web Role migrated to Windows Azure SDK 1.7
- AutoMapper added for mapping between View Model objects and Domain Model objects.
The following technologies are used for EFMVC project
- Windows Azure SDK 1.7
- ASP.NET MVC 4 RC
- ASP.NET Web API
- Entity Framework Code First 4.3
- Autofac 2.6.3
- AutoMapper 2.1
The following are the updated feature list of the EFMVC app
- Domain Driven Design (DDD)
- CRUD demo in ASP.NET MVC 4 with Entity Framework 4.3 Code First
- Generic repository for Entity Framework Code First
- Repository Pattern and Unit of Work
- Dependency Injection using Autofac
- Razor View Engine
- AutoMapper for mapping between View Model objects and Domain Model objects
- Solution Architectures using Commands(write operations), Command Handlers, Command Dispatcher
- HTTP services using ASP.NET Web API
- Dependency Injection in ASP.NET Web API
- Windows Azure Web Role
Source code
You can download the source from http://efmvc.codeplex.com/