You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to configure the project to only output the win runtime folder?
Scope
I only plan to publish this application on Windows 2016 Server so the OSX/Linux/Unix runtimes folders are not necessary. In several cases these runtimes folders contain known vulnerable dlls which lead to false positive OSA scans.
Why do i request this?
I have tried adding the win10-x64 and win10-x86 RIDs in the my project file's element:
I believe it creates a self-contained deployment. As my publish directory goes from being 55MB to 120MB and from 237 files to 482 files. It also matches the output if I included the --self-contained flag.
Thank you for your time and help!
The text was updated successfully, but these errors were encountered:
Topic
Target specific .NET Core Runtimes, specifically the
win
RID because that is the only platform I am targeting.On my CI/CD server I publish my applications with this command:
dotnet publish -c Release -o ..\publish
It outputs a runtimes directory with the following sub-directories:
Is there a way to configure the project to only output the
win
runtime folder?Scope
I only plan to publish this application on Windows 2016 Server so the OSX/Linux/Unix runtimes folders are not necessary. In several cases these
runtimes
folders contain known vulnerabledlls
which lead to false positive OSA scans.Why do i request this?
I have tried adding the win10-x64 and win10-x86 RIDs in the my project file's element:
The output of adding the RIDs to my csproj files is the same as if I did not specify the RIDs in those files.
When I run CI/CD command example
dotnet publish -c Release -r win10-x86 -o ..\publish
I believe it creates a self-contained deployment. As my publish directory goes from being 55MB to 120MB and from 237 files to 482 files. It also matches the output if I included the
--self-contained
flag.Thank you for your time and help!
The text was updated successfully, but these errors were encountered: