Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Have you referred to this guide: <a href="http://www.codeplex.com/TFSGuide" rel="noreferrer">http://www.codeplex.com/TFSGuide</a></p> <p>I just got through writing a TFS guide for our company and we followed most of the best practice recommendations from that guide.</p> <p>The structure we are using is this:</p> <pre><code>TeamProject1 Main Source ClassLibrary1 ClassLibrary2 CommonCodeLibrary TeamProject1Web Releases Release1 Source ClassLibrary1 ClassLibrary2 CommonCodeLibrary TeamProject1Web Release2 Source ClassLibrary1 ClassLibrary2 CommonCodeLibrary TeamProject1Web TeamProject2 Main Source ClassLibrary1 CommonCodeLibrary TeamProject2Web Releases Release1 Source ClassLibrary1 CommonCodeLibrary TeamProject2Web Release2 Source ClassLibrary1 CommonCodeLibrary TeamProject2Web SharedTeamProject //this would represent a set of code that's used in other team projects Main Source CommonCodeLibrary Releases Release1 Source CommonCodeLibrary Release2 Source CommonCodeLibrary </code></pre> <p>Basically, we branch the Main\Source project to the Releases\Releasex branch when it's time to do a release.</p> <p>For code that's shared across multiple projects, we create a separate team project for that code and then we branch it into the individual team projects. In the example below, SharedTeamProject represents shared code. We would branch CommonCodeLibrary, for example, into teach of the Main\Source folders for the individual team projects.</p> <p>For customer specific releases, you could just create the proper release branches for them.</p> <p>I think the main thing is to come up with a scheme that your team agrees (mostly) on, understands, and is willing to follow. Make sure that scheme is documented well and that it's followed. Consistency in structure is one of the keys to a successful source control system. </p>
    singulars
    1. This table or related slice is empty.
    1. POTeam Foundation Server - A programmer's guide
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdcp
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. COYou're missing a development branch in my opinion.
      singulars
      1. PO
      1. USGerrie Schenck
    2. COWhere do you store other data than Code? You don't have that in your strucutre above.
      singulars
      1. PO
      1. USFilip Ekberg
    3. CO@Gerrie - I disagree. Did you have a look at the patterns and practices guide I linked to? Please refer to Chapter 5 and you'll see that this is one of the patterns Microsoft endorses (see Scenario 2). @Fillip - You can create other folders as necessary, but the idea with TFS as oppossed to SVN is that project level documentation is stored in share point portal. When you create a team project, a share point portal site is created exactly for this purpose. That's one of the things that confuses a lot of people coming from SVN to TFS, the paradigm is a bit different.
      singulars
      1. PO
      1. USdcp
 

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