Products

Solutions

Resources

Partners

Community

Blog

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesEntity Framework 4 in VS2010 for a DNN ModuleEntity Framework 4 in VS2010 for a DNN Module
Previous
 
Next
New Post
10/22/2011 7:36 AM
 
Hi,

I had exactly the same problem with EF connection strings error while trying to get EntityDataSource to work.

There are some useful resources on the web regarding the matter:
  1. http://stackoverflow.com/questions/68... (plenty of solutions)
  2. http://blogs.teamb.com/craigstuntz/20...

and there are a lot of people it helped. I've tried all of them, but neither was useful for me.

I eventually thought to get back to good old dnn templates, but all of a sudden it worked. The only thing that has changed since was a Windows Update, particularly 2 of them:

  1. Security Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB954430) and
  2. Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB973688).

This is the only difference between my non-working (faulty EF string) configuration, and the working one, so I assume this is the solution in my case.

Hope tihs helps!
- Z

 
New Post
10/22/2011 9:12 AM
 
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
 
New Post
10/23/2011 11:15 AM
 
Brandon, this sounds great, I am looking forward to it!

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/25/2011 4:49 PM
 
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...
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesEntity Framework 4 in VS2010 for a DNN ModuleEntity Framework 4 in VS2010 for a DNN Module


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out