Hi

I have a problem with connection string in Entity Framework beta 3 in my custom module. In portal web.config there is connection string called SiteSqlServer - it is connection string to database. So normallly e.g.: when I use LINQ to SQL I only set connection string to SiteSqlServer and there was no problem. But Entity Framework creates (during createing it) its own connection string(and adds it to web.config), but when I move my module to production server there is a problem because there is no Entity Framework connection string there. And my question is how to create this Entity Framework connection string so that it can be used on any portal (of course based on SiteSqlServer). Is it possible?

Hi Peter,

The ObjectContext base class, from which your entity-specific context class derives, exposes a constructor that allows you to specify a connection string at runtime (the parameterless constructor calls the base constructor with the connection string specified in the designer).  This will likely be your most immediate remedy to circumventing the issue you describe.  Alternatively, you might consider deploying your own entity connection string to the web.config (based off of the SiteSqlServer string) during module instantiation.  Both approaches have their advantages.

As Sebastian saliently articulates, you will continue to have issues with the object qualifier and database owner for DNN installations that utilize these features.  There exists no current workaround for this issue (to my knowledge).

I have as an element on my to-do list an adaptive approach to both of these issues; I was able to do so for LINQ to SQL, but have not yet done so in the L2E universe.  While there are some similarities, unique difficulties exist in the latter domain.

Hope this gets you pointed in the right direction.  Best of luck -- L2E in the DNN framework is very bleeding-edge stuff.

Brandon

Hi Jan,

That's a great catch, and certainly part of any forward-looking DotNetNuke integrational implementation.

Brandon