Stephen,

This works pretty well for us in VSS

... some level of higher hierarchy dependent on your client/app structure
   ThisApp
      dev
         index.ascx
         index.ascx.cs
      test
         index.ascx
         index.ascx.cs
      prod
         index.ascx
         index.ascx.cs

Where you add the files to the dev subtree. and then SHARE them down into the other folders. Developers to all their work in the dev subtree. When something is ready to promote to test, you pin the desired version in the test subtree and it gets deployed to the test webserver. When QA blesses it the pin is promoted in the prod subtree and deployed to the prod webserver.

>Doing a segment of iterations on existing applicaiton.
>
>I have to separate approximately 3 groups of code base on the same app/same actual pages.
>
>Time frame is weekly where I will have my currWork, Released to QA, Passed to Stage.
>
>No we don't have TFS, and I can get into ChangeManDS late Feb for training. :)
>
>So any ideas on how to keep this managed?
>
>Should I make manual branches in code base on my personal dev box? Maybe keep the Fri data as part of it's name?
>
>Or is there a better way?
>
>Never used SourceSafe for ASP.NET content, is that another thing to consider?