-
Notifications
You must be signed in to change notification settings - Fork 179
Re-Bootstrap Source Build to .NET 10.0.100-preview.7.25322.101 #1289
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
Conversation
This is because |
Getting these errors in the Microsoft build:
@ViktorHofer - Do you know what might be the cause? |
<Usages>
<Usage Id="Microsoft.CodeAnalysis.Analyzers" Version="5.0.0-1.25315.102" File="artifacts/obj/aspnetcore/project-assets-json/obj/Microsoft.AspNetCore.App.Analyzers/project.assets.json" />
<Usage Id="Microsoft.CodeAnalysis.Analyzers" Version="5.0.0-1.25315.102" File="artifacts/obj/aspnetcore/project-assets-json/obj/Microsoft.AspNetCore.App.CodeFixes/project.assets.json" />
</Usages> Now we're getting prebuilts for the same packages but for a newer version than before, which now represents the N-1 version again. I need to re-evaluate my assumptions of the versioning here with Roslyn to understand what's going on. |
Apparently I've forgotten my only analysis for a month ago: #400 (comment). The fix for this is to re-bootstrap targeting the SB artifacts from the stage 2 output until dotnet/roslyn#78643 is fixed. |
@jkoritzinsky for the above question on ILCompiler.Reflection.ReadyToRun |
@jkoritzinsky - Can you take a look at the R2R issue? #1289 (comment) |
The failure is due to the RID-specific tool packages support triggering on |
Looking into possible solutions/workarounds now |
Re-Bootstrap Source Build to .NET 10.0.100-preview.7.25322.101
Fixes dotnet/source-build#5254