Hi.

We have a few applications built on the DNN platform (version 4.9, if that matters), comprising of a series of individual modules.  All of our modules are under source control using TFS.

For our regular web applications, after a production roll, we branch the code in to a specific production branch, so we can perform defect fixes on production code.  New development happens in the trunk of the project.  Any defect fixes are then merged from the branch back in to the trunk.  This way we always have a version under source control that matches what is in production.

With our modules, since they all live under the DesktopModules folder, branching to another directory won't work. The module files will not be in the correct location to run the branched code.  We do have times where we release a module, start new development on it and have to rollback changes so we can fix a production defect.

What I am wondering is if anyone out there is using DNN modules similarly, and if so, how you are handling branching your module code so that you can work on a production version of your code and a development version of your code and have it all work.

Thanks.