0

I have 2 projects in my solution: project A and B. I added a dll reference to my project A. Now when i build the project A the dll is copied to the project A output directory. Now if i reference project to project A from project B, the dll is newer copied to projects B output folder. Why is that?

Is this by design from Microsoft?

hs2d
  • 5,523
  • 18
  • 58
  • 97

3 Answers3

1

Is this by design from Microsoft?

Yes.

gdoron is supporting Monica
  • 136,782
  • 49
  • 273
  • 342
1

You can choose wether the assemblies are copied by setting the "copy to output" option.

In my projects the once which produce a runtime (Console,App, unit tests)..), are copying refs to local. This is important because without that the app wouldn't run.

The other projects (components and so on) are bulding to a central binary folder and are not copying their references, becuase they were taken from there. This saves a huge amount of build time.

Boas Enkler
  • 11,465
  • 12
  • 61
  • 128
0

To set the Copy Local property to True or False In Solution Explorer, click the Show All Files button to display the References node. Open the References node for the project. Right-click a reference in the References list, and click Properties. The properties associated with that reference appear in a list in the Properties window. In the Properties window, change the Copy Local property to True or False.

Refer : https://msdn.microsoft.com/en-us/library/t1zz5y8c(v=vs.90).aspx

Vignesh
  • 11
  • 2