-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
C#: Update to .NET9. #17999
C#: Update to .NET9. #17999
Conversation
2d5341d
to
e6fa73e
Compare
e6fa73e
to
263a4a9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one comment. Updating .NET seems to become a bigger task every time...
def check_build_out(msg, s): | ||
lines = s.splitlines() | ||
lines = s.splitlines() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes. I will do that in a follow up as this PR can merged now.
In this PR we update the extractor to target .NET 9, which also requires that all our workflows and dependencies are updated accordingly.
This PR is paired with an internal PR. There will be a follow up PR that updates the dependencies further (including Roslyn) and also addresses some of the compiler warnings.
A couple of notes on this PR
TestRunner.cs
is required because thexunit
dependency is updated.dotnet_run
anddotnet_build
integration tests is needed because with .NET 9 the console logger is replaced with terminal logger and the latter makes some formatting of the printed text. This is also listed as a breaking change here.DCA run: https://github.com/github/codeql-dca-main/issues/24870
There are no performance regressions. The alert discrepancies on the powershell buildless project is most likely a side effect of the increased target call precision for this run (this could be mostly wobliness).