Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Verify that:</p> <ul> <li>$(SolutionToBuild) uses a relative path when referencing Product.sln</li> <li>the relative path between $/NewFeature/.../TFSBuild.proj and $/NewFeature/Product.sln is the same as it is in the Main branch.</li> </ul> <p>/ EDIT /</p> <p>Note, however, it's <em>not</em> important that $/Main and $/Branches/Feature live at the same level in the tree hierarchy. Nor should the local path on the build server matter.* All that matters is what's underneath each branch. If the <em>contents</em> is internally consistent then all of your existing build scripts should work without modification. </p> <p>For concrete examples of how I like to tie everything together, see my past answers, e.g.:</p> <ul> <li><a href="https://stackoverflow.com/questions/977881/modular-teambuilds">Modular TeamBuilds</a></li> <li><a href="https://stackoverflow.com/questions/1107008/sdlc-mangement-for-tfs-build-scripts">SDLC Mangement for TFS Build Scripts</a> </li> <li><a href="https://stackoverflow.com/questions/1374380/where-to-put-my-database-project-in-tfs">Where to put my database project in TFS?</a></li> <li><a href="https://stackoverflow.com/questions/1217005/how-do-you-share-external-dependencies-between-visual-studio-solutions">How do you share external dependencies between Visual Studio solutions?</a></li> </ul> <p>My way is not the only way, but I can attest that it works better than all the other variations I've encountered over the years :)</p> <p>*Frankly, trying to micromanage Team Build can become a lot more painful than the proposed restructuring to your MSBuild scripts. For reliability you have to place your <a href="http://blogs.msdn.com/buckh/archive/2007/07/20/tfs-2008-build-agent-configuration-options.aspx" rel="nofollow noreferrer">tfsbuildservice.exe.config customizations</a> under version control somewhere...if you own >1 build server (or might in the future) then you have to consider a change deployment strategy...you end up needing a meta-SCM process to manage your SCM process!</p>
    singulars
    1. This table or related slice is empty.
    1. POTFS build-server build of branch?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USRichard Berg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTFS build-server build of 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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Richard. The trouble is we have a legacy build that does copies, obfuscation, installers and then a copy to the drop folder after the build - so (to save a lot of work) I really hoped to map the NewFeature code in place of the Main code. I'll add an answer below with my findings so far...
      singulars
      1. PO
      1. USJason Williams
    2. COCheers for takig the time to add this detail, Richard. I'll have a good read through. I just want to sort out the TFS best practices before making massive changes, rather than going to a lot of effort and then finding out that it doesn't work that way either!
      singulars
      1. PO
      1. USJason Williams
    3. COAccepted answer, as your other answers exactly describe my planned branching structure, suggesting that I'm at least barking up the right tree :-)
      singulars
      1. PO
      1. USJason Williams
 

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