Hello DNN community,

I have a moderately complex DNN application which my company uses as a web interface for our main product line. I have been tasked with the burden of finding a way to have our portal add into an existing customers DNN portal (our portal will be a different portal number). As it stands now, our portal install method entails a fresh DNN database and files, then re-syncing the users. Any custom changes are lost.

 I am sure I can’t be the only person with this type of DNN Portal requirement. I have only been using DNN for a few months and I’m no expert, but I do know my way around. Some questions I have…

1. What happens if the customers DNN portal is an older/newer version then our portal? Would we require their portal be at least our version? 

2. I’m sure as our application changes; we will remove modules for newer better ones. Is there a simple process for removing modules?

3. My task requires this all be done though some installer (for the installer guy to build). So everything needs to be scriptable (SQL, batch files are fine).

 

Very many thanks for as much details on this subject anyone can provide.

I am in agreement with leupold.

I am sure that it could be done, but it would be a VERY manual process and personally would take a really long time to manage as you would have many identitiy columns to work with and modify.  Also it would be very hard to capture all of the potentially affected relationships.

---

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


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