VSS and VS.NET Help with simple versioning

[NervousRex]

Hello I'm trying to get an understanding of what steps I need to do for my ideal VSS setup.

What I would like is to create a project in Visual Studio, add it to source safe. (i can do this)

When I get to the point where I would like to release, I would like to create a copy of this build, and continue towards build 2....If a problem is found in the build 1, I would like to be able to open that build in Visual Studio and make the changes (and know the ways for the changes to affect or to not affect build 2).


I hope this makes sense, please ask if you need me to clarify anything.

Thanks

 

[hammy]

Hi,

We do something similar to this by using branching within VSS. We have created a Project Branch within VSS called NewDev. Within NewDev are all the individual projects that go to build our complete application, e.g.
NewDev
SalesDetails
SalesDetails.vbp
Customers.frm
.......
PurchaseDetails
PurchaseDetails.vbp
Suppliers.frm
......
etc. etc.

Any new developers that come along can just set up the working folder for NewDev and get a latest recursive version of everything.

When it is time to release we branch the code into a section within SS. In our case we branch NewDev into 2005.1. This again means that any developer that needs to work on this branch can go in and get latest version on 2005.1 and know they have all the source required for that release.

Problems - Remembering to replicate code in 2005.1 and NewDev. We put a process in place that forces all fixes to be done in the main NewDev branch prior to being done in the release branch.

Hope this helps to some degree,

Hammy.