Databases
StackOverflow2013
Postsdbo
POSource Control for multiple projects/solutions with shared libraries
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSource Control for multiple projects/solutions with shared libraries
    primarykey
    data
    text
    <p>I am currently working on a project to convert a number of Excel VBA powered workbooks to VSTO solutions. All of the workbooks will share a number of class libraries and third party assemblies, in fact most of the work is done in the class libraries. I currently have my folder structure laid out like this.</p> <pre><code>Base Libraries Assemblies Workbooks Workbook1 Workbook2 </code></pre> <p>Each of the workbooks will be its own solution, and the workbook solutions just reference the assemblies in the folder structure. My question is how would you lay out the source control? Would you start the repository at the base? Or would you create a repository for each workbook solution? Would you rearrange the folders? </p> <p>Now that we have the initial development done, we're about to have a bunch of outside developers come on to the project to helps us convert the rest of the workbooks and I really like the idea of them being able to check out from the base directory and having all of the dependencies ready to go. I also worry that there are other concerns that come with having 20+ solutions/projects under one source control repository. </p> <p>I want everything to be as simple as possible for people joining the project but I don't want to sacrifice long term usability. In my mind I've been going back and forth, what's simpler one repository or one repository per solution?</p> <p>I'd appreciate and insight you have, because I'm fresh out. </p> <p>Additional Information: Currently, I am using Mercurial personally, but the project will probably get moved to StarTeam unless I can make some convincing arguments for something else.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USbill_the_loser
    1. USbill_the_loser
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSource Control for multiple projects/solutions with shared libraries
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSource Control for multiple projects/solutions with shared libraries
      1. USs_t_e_v_e
      1. VTFavorite
    3. VO
      singulars
      1. POSource Control for multiple projects/solutions with shared libraries
      1. USMoSlo
      1. VTFavorite
    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