Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As I detailed in "<a href="https://stackoverflow.com/questions/1979832/team-foundation-server-and-branching-characteristics-compared-to-others/1980560#1980560">Team Foundation Server and branching characteristics, compared to others</a>", the branching model of TFS has evolved quite a bit between TFS2008 and TFS2010.<br> The <a href="http://tfsbranchingguideiii.codeplex.com/" rel="nofollow noreferrer">TFS Branching Guide</a> and <a href="http://branchingguidance.codeplex.com/" rel="nofollow noreferrer">Branching Guidance</a> can help.</p> <p>See <a href="http://tfsbranchingguideiii.codeplex.com/Thread/View.aspx?ThreadId=213780" rel="nofollow noreferrer">this thread</a> for more details on branch management:</p> <blockquote> <p>In TFS 2010, a user must have Manage Branch permission set to Allow for a given path to do the following:</p> </blockquote> <ul> <li>Convert folders to branches (and branches back to folders)</li> <li>Update metadata for a branch (i.e. owner, description)</li> <li>Create additional child branches from the original branch</li> <li>Change the relationships between branches with merge relationships (i.e. reparenting branches)</li> </ul> <p>W In TFS 2010, a user must have Merge permission set to Allow for a given path can do the following:</p> <ul> <li>Pend merge operations on branches, folders, and files under the specified path</li> </ul> <blockquote> <p>Manage Branch and Merge permissions are new for TFS 2010.</p> <p>Branching in TFS 2010 is a server-side operation.<br> Presumably, if you have a team of developers and you grant them check-in and check-out permissions without merge or manage branch permissions - these developers would be able to create workspaces that map whatever branches they need to work on to local folders on their hard drive.</p> <p>In VS 2010, Branches are now a first-class object and as such have a branch icon that easily distinguishes a branch from a folder (with a folder icon).</p> </blockquote> <p>See also <a href="http://tfsbranchingguideiii.codeplex.com/Thread/View.aspx?ThreadId=81574" rel="nofollow noreferrer">this thread</a> with a scenario closer to your situation.</p> <blockquote> <p>For shared libraries, I generally prefer using file references rather than project references.<br> I would have a separate TeamProject for developing the source code for these libraries.<br> You could deploy the assemblies to a shared folder and reference these assemblies from the various projects that use them.<br> This approach would permit you to have multiple versions of the assemblies. Each project would create file references to the particular version they require.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POTFS2010 Branching into a subfolder of another branch
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVonC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTFS2010 Branching into a subfolder of another branch
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload