Last post Oct 09, 2008 12:38 PM by Denis_dh
Oct 06, 2008 07:06 AM|Denis_dh|LINK
We're looking to setup a Dev environment starting with 3 developers and a network admin. We have a new box that has several virtual server OS's on it:
DevWeb1, DevDB1, UATWeb1, UATDB1, LiveWeb1, LiveDB1
These are intended to emulate a production environment that will allow for code to be developed, tested and deployed in a controlled manner. We've purchased a Professional MSDN subscription and are now looking at how we should rollout VS and VSS. It is envisaged
that the Developers with work from their machine and point VS to the code on the servers, not sure if this is the best solution or if there are other options. Our Head of IT has asked to have Cruise Control installed. This is software I was previously unaware
What I'm looking for is some input with regard to what we have done so far and what we need to do to configure the software so that things run smoothly from a file versioning, multi user access and movement point. I'm also looking for advice from those of
you that have been through this and to see if we need to do more than install VS and VSS
Oct 09, 2008 08:53 AM|pure.krome|LINK
Assumptions: your MSDN subscription has access to the following software:-
b) Team Foundation Server.
Please don't use VSS -> it's old and outdated. Yeah, it still works, but instead, it's been replaced by Team Foundation Server. It's awesome. U can have multi-checkout, branching and merging, etc. etc. all the things u expect from a source control product.
That said, this isn't the place to debate TFS vs Others (eg. Cruise Control) ... chat about that elsewhere.
a) Install TFS on a single machine somewhere. This will be where all your code will be stored. (Hint: don't forget to include a backup procedure .. but that's a problem for another day.. lets get u started first).
b) Install VS2008 on your developer machines.
c) Install TFS Explorer and VS2008 SP1 on your developer machines, to patch the product. TFS Explorer gives u access to your source code, project discussion, etc. (all the TFS magic goodies)
d) Install Web Deployment Projects on each developers machine, or at least for the person who will be in charge of deployment.
e) Create your solution with your project(s). Add it to source control. Don't forget to add a Web Deployment Project, to the solution.
f) create some solution configurations -> eg. Dev / UAT / Live
g) Modify your web deployment project so it knows where to deploy your web site, based on which solution configuration is selected. Eg. when u're in UAT configuration, your deployment will copy the site to the UAT shared folder which is where you're uat website
h) check that stuff in .. and ask all the developers to get latest, etc.
i) program away.
Note: TFS is more than just source control, but that's out of the scope of this discussion. U just need source control/nice development environment plus a deployment option.
Oct 09, 2008 12:38 PM|Denis_dh|LINK
Hadn't come across TFS before. Done a little research and it looks interesting but from my reading it may be over kill for a small operation like ours.