Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The problem with your build configuration is the following: say you have 3 projects and 2 solutions.</p> <pre><code>Solution1 - Project1 - Project2 Solution2 - Project1 - Project3 </code></pre> <p>All of a sudden, building Solution2 builds <em>part</em> of the code for Solution1, leaving it in an invalid state (the latest binaries are either incompatible or did not need to be built).</p> <p>Every project should be included in a single solution. Other solutions can rely on, but should not actively change the code of those projects. In this way, they can reference a built DLL because there's no reason to rebuild the external dependencies.</p> <p>To summarize, you should take some time and restructure your solutions to meet the following conditions:</p> <ul> <li>Every project is included in exactly one solution.</li> <li>If a project depends on another project within the same solution, make it a project reference.</li> <li>If a project depends on another project in a <em>different</em> solution, make it a DLL reference.</li> </ul> <p>In addition to the above, I recommend creating an "Externals" directory for placing builds in when they are referenced by other solutions. Say you restructure to the following:</p> <pre><code>Solution1 - Project1 - Project2 -&gt; reference project Project1 Solution2 - Project3 -&gt; reference Project1.dll </code></pre> <p>In this case, you'd place copies of Project1.dll and Project1.pdb in <code>Externals\Project1\Debug</code> and <code>Externals\Project1\Release</code>, and reference <code>External\Project1\$(Configuration)\Project1.dll</code> in Project3. Only update the builds in the Externals directory when you are ready to push the build to all your other solutions.</p>
    singulars
    1. This table or related slice is empty.
    1. POManaging .NET assembly dependencies by dll reference rather than by project reference in VS
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSam Harwell
    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. COThanks for the reply.I have edited my question.
      singulars
      1. PO
      1. USmark
    2. COOk, grt advise. Adding to above: How to manage version control for the published Project.dll ? I hope Project3 picks Project1.dll from version control.
      singulars
      1. PO
      1. USMunish Goyal
 

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