-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Introduce Polly.Core #1053
Introduce Polly.Core #1053
Conversation
src/Polly.Core/Polly.Core.csproj
Outdated
<Project Sdk="Microsoft.NET.Sdk"> | ||
|
||
<PropertyGroup> | ||
<TargetFrameworks>netstandard2.0;net461;net472;net6.0;net7.0</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.
I don't think you need net472 here.
And in general, I recommend listing the TFMs from most recent to oldest. That way, when VS opens up, it will default to showing you the latest TFM.
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.
Good point, adjusted these.
The issue or feature being addressed
This PR adds a new
Polly.Core
project where the V8 API will be implemented.Right from the start we want to enforce high code quality by:
Details on the issue fix or feature implementation
This PR prepares the Polly builds for the new project and does some cleanup around the build infrastructure. Mostly just moving some MSBuild properties to a props/targets to promote the reusability.
The size of this PR is somehow inflated because of the analyzer rules in
eng/analyzers
, these are just recommended rules I copied from our code base and that we are using in production libraries.Confirm the following