Hi,

We've been struggling with using DNN (ver 4.0.3) on a large team where we currently have 2 portals (about to increase to 3 and more). Team members constantly keep adding new modules and make changes to both the portals. What we have been doing so far is to ask team members to log on to a common integration server and repeat the changes. Is there a better way to handle this in development phase. How have u people handled this.

The problems I see with this approach are:

1. We do not have a link between the DNN database and our code in repository. Ideally I would love to check in my code into repository and at the same time check in "some files" which contain my DNN modules definitions, page definitions and settings.
   
2. I do not have the option of making changes on my machine and check them in somewhere.
3. The option of asking different portals to integrate on different machines and bring all their changes to the common environment seems missing.

Is there something wrong with our understanding? How are people supposed to use DNN on an application with large number of developers building multiple portals.

hi
I'm sorry I took so long to reply. Im actually stumped by a few things. What exactly did you mean by packaging and installing a module. We use cruise control right now to monitor checkins to VSS and automatically compile all the code. Can I also make it automatically install all modules that we develop?

There is another concern that we have. We have multiple people creating pages on a portal. They add modules onto a new page. Find settings that give them the desired look and feel. Modify some of the html (since some of our modules are quite flexible). We would like to be able to check in these pages that each person creates and automatically integrate all the pages into one portal. How could we go about doing this?