We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET CLI (or NuGet) doesn't care about the "debug"/"release" folder names and always copies libraries in both configurations.
Background: I'm building an non-packaged app which hosts a UWP control.
dotnet new console dotnet add package Microsoft.VCRTForwarders.140 --version 1.0.6 dotnet publish -c Release -r win10-x64 -p:Platform=x64
Only release libraries are copied to the output directory.
Both debug and release libraries are copied to the output directory.
The text was updated successfully, but these errors were encountered:
manodasanW
No branches or pull requests
.NET CLI (or NuGet) doesn't care about the "debug"/"release" folder names and always copies libraries in both configurations.
Background: I'm building an non-packaged app which hosts a UWP control.
Steps to reproduce
Expected behaviors
Only release libraries are copied to the output directory.
Actual behaviors
Both debug and release libraries are copied to the output directory.
The text was updated successfully, but these errors were encountered: