-
Notifications
You must be signed in to change notification settings - Fork 609
Update Microsoft.Extensions.Logging to v7.0.0, drop netcoreap3.1 support #1990
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
Changes from all commits
4f1e214
9e0bedd
76f8032
9b19856
bcd31ab
a5e003b
46a79fc
ef87e2a
47c16aa
0b67265
02bef57
1e78ed5
a43a47f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,7 +12,7 @@ | |
|
|
||
| <IncludeDotNetCli>true</IncludeDotNetCli> | ||
| <DotNetCliPackageType>sdk</DotNetCliPackageType> | ||
| <DotNetCliVersion>3.1.405</DotNetCliVersion> | ||
| <DotNetCliVersion>6.0.400</DotNetCliVersion> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think that you can make the changes to this file like you are doing here. This depends on on some Helix infrastructure, so we should make sure which version can be used.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This part appears to be working (see log from build), the problem is that it's not finding a matching xunit-console binary. And I don't know where that one is referenced (this project file only mentions the arguments to it, but not the binary itself, it seems) |
||
|
|
||
| <EnableAzurePipelinesReporter Condition="'$(SYSTEM_ACCESSTOKEN)' != ''">true</EnableAzurePipelinesReporter> | ||
| <TestRunNamePrefix>$(AGENT_JOBNAME)</TestRunNamePrefix> | ||
|
|
@@ -34,7 +34,7 @@ | |
| <ItemGroup Condition="'$(TestOS)' == 'Unix'"> | ||
| <!-- Xunit project to test --> | ||
| <XUnitProject Include="..\src\System.Device.Gpio.Tests\System.Device.Gpio.Tests.csproj"> | ||
| <TargetFramework>netcoreapp3.1</TargetFramework> | ||
| <TargetFramework>net6.0</TargetFramework> | ||
| <RuntimeTargetFramework>netcoreapp2.0</RuntimeTargetFramework> | ||
| </XUnitProject> | ||
| <!-- Target queues --> | ||
|
|
||
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.
Is there a reason why we have to make these changes together with the nca3.1 changes? I think it would be better to isolate the two.
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.
It's actually the other way round: The package updates require the nca3.1 changes, because the newer packages are not supported on nca3.1 any more.
It's probably possible to separate the two (and merge the 3.1 change first), if that's really required.