March 11, 2010
Best sellers

Classifieds With Friendly URL DNN 4.x.x and 5.x.x
List Price: $45.00
Price: $39.00
You Save: $6.00

Events Listings with Friendly URLs DNN 4.x.x and 5.x.x
List Price: $40.00
Price: $35.00
You Save: $5.00

Quiz Module 3 Modules in one package for DNN 4.x.x and 5.x.x
List Price: $55.00
Price: $49.00
You Save: $6.00

 

Print  Minimize
Recent Email Problem

Hi

I will be on vacation till Christmas and may not be able to access emails all the time.

Prashant

Print  Minimize
Latest DnnMine News

Current Articles | Categories | Search | Syndication

LINQ and DotNetNuke - Creating a compiled module - Part II

 
 

Building the UI: Really , really...easy 

Right click on the DNNLINQSample module project and add a reference to the DNNLinqDBConn project.

Drag and drop a LinqDataSource onto the ViewDNNLinqSample.ascx file.

Configure the LinqDataSource as shown the steps below:

 

Step 1:

Choose the data context from the DNNLinqDBConn project as the datacontext 

 
 

 

Step 2: 

Choose the LinqSampleDB table

Click on Advanced and enable Edit, Delete and Insert operations.

Click Ok 

 

 

Step 3: 

Drage and drop a ListViewControl onto the ViewDNNLinqSample.ascx

Specify the DataSource to be LinqDataSource1

Then, click on the menu Configure ListView and Enable Editing, Inserting and Deleting 

 

 
 
Note: Deleting the web.config from the module
 
If Visual Studio has added a web.config to your module project now might be a good time to delete it. It will give you an error of you try to run this module in DotNetNuke.
 

Step 4: 

 Log into your DNN installation as Host and navigate to Import Manifest

Choose the dnn file for your module and click "Import manifest"

 

Step 5:

Create a new page and select the module from the list of module to drop onto your page.

 

 
Your module should look like this:
 
 

 
Enter some data to test you module:
 
 

 
Thats it!
 
This is a very basic example to demonstrate the techinique that can be used to use LINQ and DotNetNuke together. My personal preference is to use LINQ only for the dataobjects that are pertinent to my module and continue using the DataProvider module for any DotNetNuke core data objects.
This way we wont break anything even if the core changes.
 
 

posted @ Monday, September 07, 2009 8:36 AM by host

Previous Page | Next Page

COMMENTS

Currently, there are no comments. Be the first to post one!
Click here to post a comment
Print  Minimize
Outsource your DotNetNuke QA

 

You have a great idea for a pathbreaking DotNetNuke module
After a lot of time and effort you have developled the module.
Off to the marketplace you say....but not so fast. 

Have you tested it enough?

If you are looking for reliable partner who can undertake DotNetNuke module QA, look no further.
We understand DotNetNuke development and QA

DnnMine offers expertise in

  • Manual installation testing on multiple DNN versions

  • Defect verification

  • Functional testing

  • Testing multiple modules that work in tandem

  • Browser compatibility (IE,FireFox, Chrome, Safari)

  • Prompt communication regarding issues

  • Flexible approach and pricing specifically for your requirements

Click here to contact us

Print  Minimize
 

Copyright 2007 by dnnmine.com
 DotNetNuke  |  Terms Of Use  |  Privacy Statement