Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>TFS really likes for all dependencies of a project to be inside one folder. I would restructure your folder layout quite a bit. Here's how I would do it.</p> <pre><code>TeamProject SecretApplication SharedLibrary1 Application1 SharedLibrary1 SharedLibrary1 ConsultantApplication1 SharedLibrary1 </code></pre> <p>Here's the detail... </p> <p>Notice how all the apps are peers? SharedLibraries are shared/branched into the apps that use them. That way apps can move forward at their own pace and pull down shared changes at their own pace, and merge their changes to shared code back at their own pace. TeamProject->SharedLibrary1 is the "mainline" for SharedLibrary1. Everywhere else you see SharedLibrary1, it's a branch. Each application folder is its own "mainline", making your structure more app-centric than "all our work" centric.</p> <p>With this setup, you merely make a branch of Application1 and call it ConsultantApplication1. That way you can setup your security to allow your consultants to only see that one app and all its dependencies. They can merge and pull at will. Well, they won't be able to merge without seeing the source project, but you can. All other apps in your team project will be invisible to them.</p> <p>Let me know if I've misunderstood something or there are some requirements preventing you from using a structure like this. If there's a secret shared library under Application1, we'll have to think on this some more, but I think that would have compilation issues anyway. Regardless, placing all dependencies for an app under a single folder helps a ton and is a great practice.</p>
    singulars
    1. This table or related slice is empty.
    1. POBranch selectively in TFS
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTim Hardy
    1. USTim Hardy
    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. This table or related slice is empty.
    1. COIt would be nice, but it's simply not feasible in our situation. We have a project/folder structure that works well for our developers; this is a new requirement that we didn't foresee.
      singulars
      1. PO
      1. USTrueWill
    2. COIncidentally, doing it like this means that SecretApplication and Application1 cannot share a library project unless it's copied (shudder) or pre-compiled. VS has no problem compiling projects from another folder.
      singulars
      1. PO
      1. USTrueWill
    3. COVS can compile projects from another folder, but you won't get any of the source control benefits with that setup. If SecretApplication and Application1 both have branches of SharedLibrary1, then they can diverge in their development. They're shielded from the changes some other app might have had to make in the library and can get latest or merge when they are ready. This is the major benefit of not simply linking to the library in its home/source folder. I hear you on pre-existing conditions though. It can be hard to restructure your source folders on a large legacy app.
      singulars
      1. PO
      1. USTim Hardy
 

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