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...DNN Development Best PracticeDNN Development Best Practice
Previous
 
Next
New Post
1/7/2008 8:26 PM
 

Hi All,

I would like to know what is the best practice for DNN development.

1. If I want to change some code on one module, do I need to open the whole dnn solution?
2. Do I need to compile everytime I made changes to the module?
3. I have dev server for my apps, but everytime I want to open the solution through my local computer, I always getting the error: "Unable to open the Web 'http://localhost/Dotnetnuke_2'. How to open/change the file on dev server through my local computer/laptop using VS2005?

Thanks.

 
New Post
1/7/2008 9:16 PM
 

1, You can just open the individual project of this module, but most time, open the whole solution is more convenient for you development.

2, If you use the Source pack, you should compile everytime, if you use StartKit, you don't need.

3, You should modify the DotNetNuke.sln file or put the DotNetNuke file under the Dotnetnuke_2 virtual directory of you local web site. For detail information , please refer to the Module Development help documents.

 
New Post
1/7/2008 11:13 PM
 

I saw that nicholas replied my thread, but I cannot see the message. Please help...

 
New Post
1/7/2008 11:24 PM
 

Just a thought, this is a moderated forum, it might just take a bit for his response to get apporved.

 
New Post
1/8/2008 8:38 AM
 

Hi Nicholas,

I thank you for your promptly reply.

1. Where I can find each individual module project, is it on the Desktop Module folder? 
2. I am using a source pack, so, I have to compile each time made changes to the module. Do I have to build solution or compile only the specified module?
3. Lastly, after building about 1 year of DNN apps, I feel that I need to setup a development to production environment correctly and follow the procedure. What I would like to have is one dev server with VS and SQL Server install on that machine. One staging server and one production server. Any development should happen on the dev server such as try out a new module, etc. However, what is the best practice for this such of complete environment? How do we push the latest file back to the production without losing any current data on production? I would like to hear from each one of you who experience using DNN as live apps and the best practice to maintain it. Please point me to the good article as well. Thanks.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Development Best PracticeDNN Development Best Practice


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