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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Getting my head Round DNN and existing applicationsGetting my head Round DNN and existing applications
Previous
 
Next
New Post
2/9/2007 9:59 AM
 

Ive got a number of existing customers who have sited that are well deeloped in asp.net, who may benefit from being moved across to dnn (Mainly from a content management perspective.)

Some of these would be straight forward ports, but others have additional business modules, or other datbases attached to them. How would you recommend I go about (minimal stress) migrating them.

would you recommend keeping the business applicaiton and database seperate, on another server, or is it straight forwards enough to add a second database to the hosted dnn database server, and run my application alongside .NetNuke ? -  for new customers I'd look at adding my own modules that do the business logic, but I dont want to go through the pain of recreating existing (working) logic.

As an ammendment to that, one of the sites has its own user login / registration system, that then gives access to the business application. Is there any way of using the DNN registration / login system to control access to my own applications?

 

Cheers

 

Sb

 
New Post
2/9/2007 10:16 AM
 

 

Why dont you start with sites that look the easiest, that way you start to get momementum and move towards the harder ones. During that process you will learn what decisions will be best for you.  Always best to get other peoples opinions when you get stuck.

 Its easy to have multiple databases in dnn so that should probably be the preferred and keep your custom db separate. Although at some point if you develop modules you will have some elements in teh dnn framework of course. for example if you use the module settings features.

You can use dnn authentication by referencing dnn in your applications, just depends on a the requirements of your app.

 


DotNetNuke Search Engine
ASP.Net Search Engine
Email me to add your favorite sites to the search List.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Getting my head Round DNN and existing applicationsGetting my head Round DNN and existing applications


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