-
Notifications
You must be signed in to change notification settings - Fork 757
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
Update TFMs #4394
Update TFMs #4394
Conversation
<!-- This target will make sure that projects targeting netcoreapp3.1 will also have the Microsoft.Extensions.Logging.Abstractions analyzer removed. --> | ||
<!-- This target will make sure that projects targeting net462 will also have the Microsoft.Extensions.Logging.Abstractions analyzer removed. --> |
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.
@joperezr I kept this target because the comment in Microsoft.Extensions.Telemetry.Abstractions.csproj refers to both net462 and netcoreapp3.1:
Please let me know, if I misunderstood it, and these should be removed.
* Drop support for .NET Core 3.1 * Add support for .NET 6.0 * Run tests for only supported TFMs - i.e., net462;net6.0;net8.0
5582a1e
to
c8a10ac
Compare
This comment was marked as resolved.
This comment was marked as resolved.
@RussKie Where do the warnings come from? This did these just appear as a result of an analyzer upgrade? |
There are also hundreds of TBD warnings:
These are the result of (likely because of the newer SDK?): extensions/Directory.Build.targets Lines 56 to 62 in 80f8c70
As an immediate workaround I'm going to suppress [EDIT] Raised #4395 |
The newer SDK: "sdk": {
- "version": "8.0.100-rc.1.23381.2"
+ "version": "8.0.100-rc.2.23462.28"
}, |
I think we should fix the IDE0028 warnings (I'm guessing VS can do this over the whole solution). And please suppress the TBD warning for now, I'll find a suitable workaround. |
Sure. |
…stMessage.Properties has been deprecated. Use Options instead.'
b1988f2
to
6c2eb26
Compare
The build is green, good to merge 😉 |
<ConditionalNet462 Condition="'$(CustomTargetFrameworks)' == '' OR $(CustomTargetFrameworks.Contains('net462'))">;net462</ConditionalNet462> | ||
|
||
<!-- All the .NET TFMs we're testing against --> | ||
<TestNetCoreTargetFrameworks>$(NetCoreTargetFrameworks)</TestNetCoreTargetFrameworks> | ||
<TestNetCoreTargetFrameworks Condition="'$(CustomTargetFrameworks)' == ''">$(TestNetCoreTargetFrameworks);net7.0;net6.0</TestNetCoreTargetFrameworks> | ||
<TestNetCoreTargetFrameworks Condition="'$(CustomTargetFrameworks)' == ''">$(TestNetCoreTargetFrameworks);net6.0</TestNetCoreTargetFrameworks> |
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.
@RussKie now this emits a warning that looks like:
Error occurred while restoring NuGet packages: Invalid restore input. The original target frameworks value must match the aliases. Original target frameworks: net8.0;net6.0;net6.0;net462, aliases: net8.0;net6.0;net462. Input files: C:\Users\...\source\dotnet-ext\test\Generators\Microsoft.Gen.AutoClient\Generated\Microsoft.Gen.AutoClient
I.e., the net6.0
TFM is listed twice for test projects that have <TargetFrameworks>$(TestNetCoreTargetFrameworks)</TargetFrameworks>
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.
Can either you or @RussKie log an issue to fix this so that we make sure it is fixed? How come we aren't seeing this error in CI?
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.
Microsoft Reviewers: Open in CodeFlow