MSBuild 15 don't copy to relative output path libraries that not included in “reference” block of NuGet package
I have a problem with MSBuild 15 and copying to output path libraries that not included in "reference" block of NuGet package. <metadata> <references> <reference file="ReferencedDLL.dll" /> </references> </metadata> <files> <file src="bin\ReferencedDLL.dll" target="lib\net461" /> <!-- These ones --> <file src="bin\SomeOtherDLLs*.dll" target="lib\net461" /> </files> If OutputPath is relative then SomeOtherDLLs*.dll are not copied to output (ex. bin/debug). If OutputPath is absolute thats all right. This problem appeared when I migrate my NuGet references to new <PackageReference> spec. Of course I can put $(MSBuildThisFileDirectory) in <OutputPath> property at project file <OutputPath>$(MSBuildThisFileDirectory)\bin\$(Configuration)\</OutputPath> or use build/*.target in package. But I can't understand why is the behavior different and these problems manifests only when using relative paths?
Building Windows 10 Mobile app using Visual Studio Team Services
msbuild in CI server
How to override ApplicationVersion for Publish target in MSBuild
Failed to execute Task error with msbuild step
Building Xamarin Android on TFS - how to download Nuget packages
Incremental MS Build
Teamcity display error message instead exit code
MSBuild target Get List of newer or older files
Rider Error:CS0041: Unexpected error writing debug information — 'The method or operation is not implemented.'
Include additional files in build using MSBuild
Error integration SonarQube Msbuild runner with TeamCity
MSBuild shared .targets file
How to use MSBuild transform when ItemGroup files all have identical names?
Team Services build windows service to the deploy folder
MSBuild ResolveAssemblyReference task is very slow after loading Visual Studio
How do I get the the expected output from a TFS 2015 build (to match my XAML build)?