dotnet build with runtime specified does not create the right output
See original GitHub issueMoved from https://github.com/dotnet/cli/issues/5039 on behalf of @Fabi, @nguerrera
Steps to reproduce
- Install Visual Studio 2017 RC
- Follow the “Deploying a simple self-contained deployment” part from https://docs.microsoft.com/en-us/dotnet/articles/core/preview3/deploying/ until step 5
Expected behavior
After running the dotnet build -r win10-x64 command a folder with the build files (including an .exe file not only dll) should be created at “.\bin\Debug\netcoreapp1.0<runtime_identifier>”
Actual behavior
There is no runtime folder with executables generated. That only works with the publish command now. Before on json based project files it worked fine.
Environment data
dotnet --info
output:
.NET Command Line Tools (1.0.0-preview4-004233)
Product Information:
Version: 1.0.0-preview4-004233
Commit SHA-1 hash: 8cec61c6f7
Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\1.0.0-preview4-004233
@nguerrera this is the standalone publish scenario. It should work like this:
on build
Build produces the portable output as well as a RID-specific output. The RID-specific output contains the portable output + the appropriate RID-specific host for the app. That host still uses deps.json, etc. to load Shared Framework artifacts from the nuget cache
on publish
The publish output is RID specific. It includes everything from the RID-specific build output + everything from the RID-specific Shared Framework. The publish output can now be zip’d and then deployed to any host with a matching RID.
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (8 by maintainers)
We decided not to change the default output folder this late in the cycle. You can set AppendRuntimeIdentifierToOutputputPath=true to opt in to that behavior.
They are not generated at all on build. I searched them but never found them, so I guess they are not generated.