How to setup a DotNetNuke Development Environment with Source Control?

Posted by Joosh21 on Stack Overflow See other posts from Stack Overflow or by Joosh21
Published on 2009-11-30T22:34:04Z Indexed on 2010/04/01 3:53 UTC
Read the original article Hit count: 416

My team is developing a new DotNetNuke web application and would like to know what is recommended to setup a development environment with source control and automated builds? We would like to keep the DNN source code separate from our custom modules and extensions source code.

The DotNetNuke Compiled Module template for Visual Studio wants us to store the source code in the DesktopModules directory of the DNN source code and output to the DNN source code bin directory. Is this the recommended structure? I would rather keep the files in different locations, but then it becomes more difficult to run and debug locally as it would require an install of the module for each change. Also, how should an automated build deploy any changes?

How have others set this up? Is there a recommended best practice?

© Stack Overflow or respective owner

Related posts about dotnetnuke

Related posts about build-automation