Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am importing a website into TFS that is stored in SourceSafe as

$/MyApp 1.0
$/MyApp 2.0
$/MyApp 3.0
$/MyApp 3.5

Should I import this as several distinct projects (MyApp1.0 ... ) or as one project called "MyApp"?

share|improve this question

closed as not constructive by Jim G., Walter, thorsten müller, Robert Harvey, BЈовић Nov 30 '12 at 7:19

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 1 down vote accepted

As a single "MyApp", then use a branching strategy...

You should consider following a standard branching strategy that contains Development, Main, and Release branches. It may take a little getting used to if you haven't dealt with branching and merging before, but it will provide benefits when it comes to managing changes when multiple teams or features being developed at the same time.

There is a group called the ALM Rangers that publish guidance on this for TFS (see links below).

TFS Rangers Branching & Merging Guide -

MSDN Article "Visual Studio TFS Branching and Merging Guidance" -

share|improve this answer

A rule of thumb is to not worry about different TFS projects except when you want different TFS templates. This means different work-item templates, different sharepoint projects sites, different reporting services spaces.

9 times out of 10 people make extra TFS projects based on what should be branches, remember, the only difference between two TFS projects is the template. If you want to use the same work-item templates etc for all your source code, put it all in one TFS project. Multiple TFS projects becomes a pain to manage over time and often is completely unnecessary.

share|improve this answer

One project named "MyApp" and then multiple branches representing each release. This article should give you a good overview of how to branch for releases:

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.