Skip to content

Fix dotnet store for netcoreapp3.0 #3345

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

Merged
merged 1 commit into from
Jun 20, 2019

Conversation

nguerrera
Copy link
Contributor

@nguerrera nguerrera commented Jun 20, 2019

Also fix msbuild batching error that caused O(N^2) redundant work, and flakiness due to race conditions between the redundant workers.

And replace ContinueOnError=WarnAndContinue with just ignoring standard error format on exec of crossgen. crossgen prior to 3.0 is notorious for spewing noise and the only thing that is reliable is the exit code. The previous approach around it was way too big of a hammer.

This is the "minimal fix" for 3.0. I am still working on a major re-design and simplification of dotnet store, but that will not likely be ready for 3.0 preview 7 and we want to have these issues fixed before then.

It is also not clear yet if we would be able to use the simplified design for all TFMs or only on netcoreapp3.0. That is because the crux of the re-design is to use the new PublishReadyToRun code as the foundation.

Also fix msbuild batching error that caused O(N^2) redundant work, and
flakiness due to race conditions between the redundant workers.
@nguerrera nguerrera marked this pull request as ready for review June 20, 2019 02:41
@nguerrera nguerrera requested a review from a team June 20, 2019 02:41
Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little fuzzy on what the problem with netcoreapp3.0 was.

But the MSBuild logic changes here: 👨‍🍳😗👌

@nguerrera
Copy link
Contributor Author

I'm a little fuzzy on what the problem with netcoreapp3.0 was.

The issue for 3.0 was basically that dotnet store does a kind of custom self-contained deployment of .net core runtime + crossgen.exe as a first step. The framework reference work broke the way it was doing it by reading nuget assets. I had to copy some of the logic for 3.0 SCD, starting here: https://github.com/dotnet/sdk/pull/3345/files#diff-272dc14b0ed4e9d846b62bb698af2f42R289

The code in these targets is pretty rough. I have a plan where I would rip this all out and just use crossgen directly without this step, as PublishReadyToRun does, but I'm not sure when I'll be able to land that change yet.

@rainersigwald
Copy link
Member

Got it, thanks. :shipit:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants