![ez7z output directory ez7z output directory](https://i.stack.imgur.com/cvK75.png)
If our project was a program (not a library) with the following configuration:
![ez7z output directory ez7z output directory](https://xlinesoft.com/asprunnerpro/docs/images/step12_asp.jpg)
We can see the output for the default settings on the following screenshot:Īs you probably notice, the library files from referenced NuGet packages are not copied to the output dir. The output location can be changed by defining OutputPath parameter or, if you only need to skip the $(TargetFramework) part, just set AppendTargetFrameworkToOutputPath=false. Let’s take a sample solution with the following projects and references structure:īy default, references to other projects are added with the following entry in the csproj file: Īfter we compile our solution, the *.dll and *.pdb files of the referenced projects are copied to the output directory - by default bin\$(Configuration)\$(TargetFramework). Documentation for new csproj format, as well as for Nuget related properties, is scattered across different MSDN documents, so I decided to create this blog post as a reference to what I’ve recently learned and discovered about the project’s options that affect the content of the output directory. The content of the output directory can be controlled with different properties inside the project file. However, sometimes we want to do something non-standard that requires a slightly different set of components in the output dir - simply speaking we expect to see there either more or fewer files. In most scenarios references added with standard mechanism (Visual Studio or dotnet cli) result in sufficient content in the output directory. NET projects, it’s much easier to manage with the project’s dependencies.