Products

Solutions

Resources

Partners

Community

Blog

About

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.0WhatWhat's the "present" standard for Import & Export?
Previous
 
Next
New Post
4/7/2007 7:19 PM
 

Hi,

I'm working on some modules and I have been studying various core modules to implement "ImportModule" and "ExportModule".

These modules have evelolved and have been added to DNN over the existence of DNN.

Some modules litterally use string concatination, some use xml serialization.

So what is the "Correct" way (there are many ways) or standard for these methods?

Thanks,

Colin


Colin Mulcahy
E: colin_mulcahy@hotmail.com
 
New Post
4/7/2007 8:02 PM
 


Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
4/8/2007 9:31 AM
 

Michael,

Thanks for post. Appreciate it.

Colin


Colin Mulcahy
E: colin_mulcahy@hotmail.com
 
New Post
4/8/2007 10:57 AM
 

Glad to help. I originally wrote some code, then Core member Stefan Cullmann who is a XML expert basically re-wrote it to make it much better.

The interface doesn't insist on a "right way or wrong way". It just expects a string. Actually you don't even have to use XML. You can use any format you want to import and export. However you usually want to use XML.

The example code is attempting to demonstrate how you would export and import relational data. This can be complicated and trickly. Stefan Cullmann's code is about as "tight" as you can get it.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
4/9/2007 10:30 AM
 

Michael,

This leads me to anthoer question I have.

When you are adding a new page (4.5.0) and you decide to copy a module from an existing page there are three options, copy module structure, copy module with content and thirdly, copy module with reference to the module content instance.

I understand options 1 and 3.

Option 2 however I need to get some clarification on.

1). Firstly, when you copy a module with its content, is it using "IPortable" to copy the content over? If so;

2). Lets say for example your module has a "Links" Table and a "Category" Table both interlinked with a third table "Category Groups". How does DNN cater for such a module when it is copying it or do I need to write a private method to handle this in IPortable?  I can understand the Survey Module as it's tables are hirearchial and you just iterate through the tables based on primary keys to construct the export and import structure.

Hopefully you might have a clearer understanding on the mechanism than i do and I'd love to get your expertise on it.

Thanks for your attention on this.

Cheers,

Colin

 


Colin Mulcahy
E: colin_mulcahy@hotmail.com
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0WhatWhat's the "present" standard for Import & Export?


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