-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Publishing as NativeAOT should not depend on AppHost #79575
Comments
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsWe currently need to build apphost because for some reason PublishAot ends up needing it in some of our test legs: runtime/eng/pipelines/runtime.yml Line 206 in cdb9f5f
Without this line, the CI fails with:
This is probably not just a test issue, but also a product issue. Historically the NativeAOT targets were just an addon to the SDK targets that hacked into the SDK (we e.g. delete outputs the SDK produces in publish and replace them with NativeAOTd stuff). The SDK probably needs to become more aware of what NativeAOT does and suppress some behaviors.
|
That error can be avoided by setting
|
Yeah, the SDK needs to be taught that PublishAot is sort of like self contained, but it doesn't need an apphost. I probably should have opened this in the SDK repo because the main fix will likely be in the SDK, but SDK repo is where issues typically go die of neglect and loneliness. |
I would imagine that with the following modifications in the SDK, we should be able to publish without the apphost requirement:
|
We do want to keep using app host for |
Fixes dotnet/runtime#79575. AppHost doesn't make any sense for PublishAot, and neither do the behaviors around SelfContained - if SelfContained is true, the bin directory gets populated with a ton of files we don't need during publish.
We currently need to build apphost because for some reason PublishAot ends up needing it in some of our test legs:
runtime/eng/pipelines/runtime.yml
Line 206 in cdb9f5f
Without this line, the CI fails with:
This is probably not just a test issue, but also a product issue. Historically the NativeAOT targets were just an addon to the SDK targets that hacked into the SDK (we e.g. delete outputs the SDK produces in publish and replace them with NativeAOTd stuff).
The SDK probably needs to become more aware of what NativeAOT does and suppress some behaviors.
The text was updated successfully, but these errors were encountered: