Rather than creating a one-off adapter for each ORM technology out there, I have recently been looking at an improved approach that wraps each as a repository and exposes a partial-monad for specification topographies that operate over multiple repository implementations (which are themselves specified at runtime).  I feel that it is a much stronger solution, and am able to run nHibernate, EF 4.0, and a standard DotNetNuke DAL side-by-side with good specification support across each.

I am actually feature-complete on everything, but haven't published my results yet.  Unfortunately, it will probably be mid-November before I can even think of doing so.

Brandon

---

Brandon Haynes
BrandonHaynes.org

Great article! It looks cool in VS: adding DataGrids and DropDowns with EntityDataSources. Eventually all the stuff is created in VS as 3 projects.

But how should it work? What after the step 29 has been accomplished?

I've tried to:

• Built the solution;
• In DNN, created a module from within the Extensions panel with only one control (the one from the article - with the DataGrid and the EntityDataSource);
• Added it to a page;
• Got the error: Error: TestModule is currently unavailable.DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

Do I miss anyhting? How should the created webusercontrol(module) be added to the DNN page?

Please advise...