DotNetNuke Modules - Making Content Portable
The last main feature of module development that we need to discuss is the implementation of IPortable.
If you’ve ever worked with other content management systems in a corporate environment, you’ll appreciate the implementation of this interface since the number one issue most organizations have is getting data from a staging area to a production area. Occasionally we’d like to get the content from production back to test or even into development. Many times we deal with this issue by just copying the database and the web application files from one area to another.
That works. But what if you want to move your content from one module on a page to another installation rather than the entire application?
That’s what IPortable does for us, as well as allowing us to move the entire site from one installation to another without having to move any files or the database.
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
