How to prevent binary file folder also being copied to output dir?

Question

I have a few class library assemblies from third parties. To help with organisation, I added a new project to my solution specially for these binaries. I didn't just add a solution folder, because I don't like that there is no physical folder there. I also like to to have these in their own project so that if I might add helpers for the original binaries I know where they are.

My project looks as follows: BinaryProj.csproj --Lib (folder) ----ab1.all ----bc3.dll ----cd4.dll

All of the above dlls are marked with 'Copy to output directory', but when I compile this project, these dlls are found under bin/Lib/....dll instead of 'bin/....dll. How can I get rid of the damnedLib`?

You're looking for [this](https://msdn.microsoft.com/en-us/library/ms165410.aspx)? — Yuval Itzchakov, Jun 17 '15 at 08:29
You could also keep them generated in `bin/Lib/....dll` and add a post build event copying the files into `bin/....dll` — Sébastien Sevrin, Jun 17 '15 at 08:36

score 0 · Accepted Answer · answered Jun 17 '15 at 08:41

0

To change the build output directory:

List item
On the menu bar, choose Project, Appname Properties. Choose the Build tab.
Choose the Browse button next to the Output path box and specify a new build output directory.

answered Jun 17 '15 at 08:41

Ravi Kumar Mistry

1,063
1
13
24

score 0 · Answer 2 · edited May 23 '17 at 12:15

You shouldn't do this. Sure, you may want to add third-party binaries to a Visual Studio (class library?) project for the overview and ease of management, but you shouldn't copy them to the output directory of that library project. The project doesn't need them, and referencing projects don't need all of them.

Just store the files wherever you want, preferably without putting them in a project, then reference the binaries from projects that need them. Then the files will be copied to the bin directory of projects that need them:

* Solution directory
|
+- ThirdParty
|  |
|  +- SomeAssembly.dll
|
+- Project1

Here Project1 will reference ..\ThirdParty\SomeAssembly.dll and copy that into its own bin directory.

If you're sure your way is the way you want, see Copy to Output Directory copies folder structure but only want to copy files to control where files are copied to.

Yeah, I supposed I could create a project purely to get a folder subordinate to the solution, then place the dependencies directly in that folder and simply reference them. They never get output to any `bin` folder other than where they are needed. — ProfK, Jul 14 '15 at 08:45

How to prevent binary file folder also being copied to output dir?

2 Answers2