Click here to Skip to main content
Rate this: bad
good
Please Sign up or sign in to vote.
See more: TFS
What is the best way to label code for a new deployment? Maybe it is better to create an new branch instead?
Posted 10-May-13 18:42pm
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 1

Probably the best resource I've found so far on using TFS and best practices:
 
http://tfsguide.codeplex.com[^]
 
[EDIT]
 
This is the one that I meant:
 
http://vsarbranchingguide.codeplex.com/[^]
 
The one above is an older book for TFS 2008 I think.
  Permalink  
v2
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 2

There is no standard for doing this. You can organize your code as you want. Personally I like to create a branch for major and minor versions. If you plan to rebuild older versions, adding labels makes this even easier.
 
I’d suggest something like this but again, there are many ways to do this
 
$\Branches
    \1.1
    \1.2 (branched from 1.1)
    \2.1 (branched from 1.2)
    \2.2 (branched from 2.1)
  Permalink  

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
0 Sergey Alexandrovich Kryukov 575
1 Kornfeld Eliyahu Peter 409
2 Maciej Los 369
3 DamithSL 196
4 OriginalGriff 188
0 OriginalGriff 6,353
1 DamithSL 4,854
2 Maciej Los 4,466
3 Kornfeld Eliyahu Peter 4,058
4 Sergey Alexandrovich Kryukov 3,897


Advertise | Privacy | Mobile
Web03 | 2.8.141220.1 | Last Updated 12 May 2013
Copyright © CodeProject, 1999-2014
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100