-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Self-contained publish/build error #21677
New issue
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
Comments
No, this is a different error (NETSDK1031, not NETSDK1179). @bradygaster, do you see this error with previous versions of the SDK or is it just with RC2? It looks like one of the project references is failing to build because it does not have a runtime identifier specified. @dsplaisted do we expect that a RID will be passed to all referenced projects when published? |
I think what's happening is we prevent the Probably we should stop |
@bradygaster Is this the line that is producing the error? https://github.com/bradygaster/TodoApp/blob/0decfd788b9952633c24afc17e2f3fe978fc1ca7/setup.ps1#L23 As an aside, this command can now be simplified, from: dotnet publish TodoApp.API\TodoApp.API.csproj --self-contained -r win-x86 -o publish\api to dotnet publish TodoApp.API\TodoApp.API.csproj --sc -a x86 -o publish\api Note: this assumes the command is always run on Windows. |
Sounds reasonable to me. |
No it was this one: |
Describe the bug
When I try to do a self-contained build and publish of an app I wish to publish to App Service prior to RC2 being on it, I am seeing errors, and as such am blocked from being able to build a self-contained publish package.
To Reproduce
I have an example repository here: https://github.com/bradygaster/TodoApp
It contains two projects in one VS solution. It also contains a
setup.ps1
file you can run to see the issue. One of the projects will build and publish just fine, the second will build but when the publish command runs this error is visible:Further technical details
My dotnet-version is:
And dotnet --info is:
@richlander asked me to file this when I showed him the issue, and that I cc @sfoslund in the issue. Thanks to the team for your hard work!
The text was updated successfully, but these errors were encountered: