Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

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
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0LinqToSQL, ObjectQualifier and Module Development?LinqToSQL, ObjectQualifier and Module Development?
Previous
 
Next
New Post
10/7/2008 9:10 AM
 
David Kieffer

Joined: 1/26/2004
Posts: 49

I am just starting module development. I want to use LinqToSQL as explained on aDefWebserver.com. (http://www.adefwebserver.com/DotNetNukeHELP/LinqTutorial/)

I want to develop modules using LinqToSQL on a development machine. I then want to install these modules on to an totally different site (say a Production site) that is currently working fine. The Production site was installed using an ObjectQualifier of ("dnn_").

Question 1:  Will I be able to do this? Develop modules using LinqToSQL and then install them (using Host/Module install) into a dnn website that was installed/setup using an ObjectQualifier of say...   "dnn_"  ?
Question 2:  The web.config still has the ObjectQualifier settting set. Should this be removed at any point?
Question 3:  why is it said that LinqToSQL module development doesn’t support the ObjectQualifer.  Can someone give an example what is meant by this and where things would fail, Break, or be an issue? At what point? I am just starting Module Development and want to know if I would be waiting my time developing modules using LinqToSQL if they are going to be installed (can’t be?) on a site that has an OjbectQualifier.
 
Thanks in Advance!
 
New Post
10/7/2008 12:25 PM
 
Mitchel Sellers


Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

www.mitchelsellers.com
Joined: 1/24/2007
Posts: 7846

LINQ to SQL does not support a dynamic object qualifier, such as the one set in the web.config, as when you are writing LINQ queries you are creating references to the exact table names.

Therefore, you CANNOT deploy a module from a development environment that doesn't have an object qualifier to a production environment that does.

Also, once you have a DNN site installed with an object qualifier, it is NOT easy to go back to not having one.

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
10/7/2008 1:48 PM
 
Michael Washington


Michael Washington's Avatar

www.LightSwitchHelpWebsite.com
Joined: 7/17/2004
Posts: 3526

The object qualifier feature was added to allow more than one DotNetNuke site to share a single database.

Linq to SQL does not support this.

My recomendation is to simply not use the object qualifier feature. If you sell modules simply state that you do not support it. Most sites do not use it.

Linq to SQL (and Linq to Entities) can speed module development by more than 80% in my personal experience.

For myself, using the full DNN DAL or the DAL+ to support the object qualifier is not an option (I do have to use the full DAL for the Survey module because it is not up to me).


Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
10/7/2008 2:00 PM
 
Michael Washington


Michael Washington's Avatar

www.LightSwitchHelpWebsite.com
Joined: 7/17/2004
Posts: 3526

One more thing. A Linq to SQL module WILL install in a site that uses the object qualifier feature, it's just that ALL DNN modules on the database will use the same instance of the module. The only time you will have a problem is if there is a second DNN site using the same database.

Therefore, if there is only ONE DNN site using a particular database you will NOT have a problem.

 


Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
10/7/2008 2:35 PM
 
Steve Fabian


Steve Fabian's Avatar

Joined: 3/4/2003
Posts: 2111

Not to jump the gun here and get everyone all excited, but there may be a solution that fully supports Linq and the DNN ObjectQualifier tag. I haven't tried this method yet but it seems that if it *does* work .. it might be the solution we're all looking for.

link: http://guy.dotnet-expertise.com/PermaLink,guid,789dd70b-73b9-4216-a479-77e19d403e38.aspx

 



 Steve Fabian
e: steve.fabian@gooddogs.com
w: http://www.gooddogs.com
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0LinqToSQL, ObjectQualifier and Module Development?LinqToSQL, ObjectQualifier and Module Development?


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