[All] Fix BuildalyzerCracker so it can work on .NET 10
#4269
+24
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BuildAlyzer has a bug with .NET 10, there is a fix available since 1 month
but not sign of a release for now.
For this reason, we want to use a local version of BuildAlyzer with the fix included
and remove our own version later on.
See:
- Buildalyzer/Buildalyzer#318
- Buildalyzer/Buildalyzer#319
To build the custom version of Buildalyzer
<PackageValidationBaselineVersion>lines (in the 3 projects). I was not able to make dotnet pack work with itdotnet build -c Release && dotnet pack -p:Version=8.0.0-fable-001