views:

30

answers:

2

All,

My dev team and I would like to setup a development environment for our ASP.NET projects. BY development environment i do not mean Visual Studio. I mean, that we have a Database Server, a Application Server and a Web Server in a 'Development Environment'.

We want to use this as our integration environment. Where the developers all work on there parts of ASP.NET Applications and then we can push our new changes up to test them as a whole.

My Question is , what is the best way to deploy our code together without stepping on our toes?

Thanks.

+3  A: 

Hello, Team Foundation Server is a good candidate for this.

Sander Pham
+1  A: 

You need a source code control methodology and with it you'll get the benefits you're searching for. SVN and other solutions in this space offer "conflict resolution" to avoid inadvertent overwriting/toe squashing.

Setup a subversion repository, get all of the developers up to speed on svn and using it.

Once you have your source under control you can consider setting up a continuous integration server which can build your code and deploy to your target environment in batch. Organizing your project code properly into trunk, tags and branches per solution will make it very easy to control what is deployed or redeployed to your dev environment at any given time.

There are other options for source code control (git, tfs, and many others) but they all offer close to the same features... SVN is one of the nicer options because it's open source, free and stable.

Another thing to consider is keeping your database schema changes in sync with your code changes. Consider using migrator.net or similar solution to enable your team to keep everything in sync through revisions, including database state.

Tahbaza
Thank you for the post, my question is on exactly what your said " consider setting up a continuous integration server which can build your code and deploy to your target environment in batch. " <-- That is my question. How do I go about doing that?
Here are some further details. Check out wikipedia's explanation (http://en.wikipedia.org/wiki/Continuous_integration) We use Hudson (http://hudson-ci.org/) but there are others. Here are a couple more references (http://www.craigberntson.com/articles/CI.pdf), (http://www.developer.com/tech/article.php/3557396/Getting-Started-with-Continuous-Integration.htm). Good luck!
Tahbaza
Thanks, I will prolly have to propse a different question. None of the above links have told me how to do CI with ASP.NET and TFS.