Just in case you are not aware, I am developing a new Visual Studio 2010 Project Template that will aid you in building DotNetNuke modules using newer technologies and architectures such as Entity Framework, WCF Data Services, Knockout.js, etc.

The Template is now hosted on CodePlex
http://dnntechtemplate.codeplex.com/ 

I have also started a Blog series explaining the template components and how to use them to build a module.  When the series is all done, I plan to build a new Community (free) module using the template as an example based on your feedback and ideas.

The “Let’s Build a Module” series

1. Project Introduction 
2. Downloading, Installing and Using the Template 
3. Output Formatting 
4. Data Access with Entity Framework and a WCF Data Service 
5. Client side Data Binding with Knockout.js 
6. Mobile Development 
7. Security 
8. Testing 
9. Packaging and Distribution 

Please Note: The template is still in the 'alpha' stage, as I plan to tweak and enhance it throughout the blog series.

All feedback, issues, comments and ideas are welcome. Please post them on the CodePlex site either on the Discussions or Issues tabs.

Thanks and hope you follow along...

The project template has been updated to version 1.2
http://dnntechtemplate.codeplex.com

Release Notes
ver 1.2 - 03.05.2012
- Moved script insertion from View markups to the module base class, to simply creation of new views
- The EF Connection string is now auto-generated in the service class, so no entries are needed in the web.config file (yeah)
- A number of environmental variables are now initialized in the module base class and injected into the views to assist the viewmodels in accessing things like the module path, edit urls, module home url, and the service url. This will greatly reduce the code you need to write in your views and view models
- Removed AutoMapper from the template, as the user of the knockout mapping library is now used to dynamically create models from service data
- Changed the code to properly construct the service URL to handle situations where the DotNetNuke site is located at the root or virtual directory or child portal