Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In case you are not creating <em>circular dependencies</em>, following is an idea: </p> <ol> <li><p>add a new <code>Class Library</code> project with a unique name, say <code>ClassLibrary1</code>, to the solution</p></li> <li><p>in the <code>Build</code> page of its project settings, config <code>Output path</code> to application output path</p></li> <li><p>in the <code>Build Events</code> page, add the following line to <code>Post-build event command line</code> block:</p> <pre><code>del "$(TargetPath)" </code></pre></li> <li><p>repeat step 1 to 3 but giving another name, say <code>ClassLibrary2</code>, and config <code>Output path</code> to the source path of <code>ClassLibrary1</code></p></li> <li><p>set <code>Project Dependancies</code> of <code>ClassLibrary1</code>, check on <code>ClassLibrary2</code></p></li> <li><p>add all other project as <em>project reference</em> to <code>ClassLibrary2</code>, leave <code>Copy Local</code> with default value <code>true</code></p></li> <li><p>build <code>ClassLibrary2</code> once, and all DLLs now are in the source path of <code>ClassLibrary1</code></p></li> <li><p>add them to references of <code>ClassLibrary1</code> and leave <code>Copy Local</code> with default value <code>true</code></p></li> <li><p>set <code>Project Dependancies</code> of application and all other projects which are not cause <em>circular dependencies</em>, check on <code>ClassLibrary1</code></p></li> <li><p>add references of other projects, from the path the DLLs were put in <code>ClassLibrary1</code></p></li> <li><p>set <code>Copy Local</code> of all these added DLLs in other projects to <code>false</code></p></li> </ol> <p>Thus, the project <code>ClassLibrary1</code> be a central control of the external libraries of your solution. Each time you <code>Rebuild Solution</code>(or just build the application), <code>ClassLibrary1</code> copies the latest DLLs add to its references to the application output folder, and deletes the DLL it generated itself named <code>ClassLibrary1.DLL</code>. The application and dependencies at either compile time or runtime would use the same version of DLLs, you don't need to do extra deploying or check each deployments. </p>
    singulars
    1. This table or related slice is empty.
    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.
 

Querying!

 
Guidance

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