-
-
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
Validate v8 build with .NET 8 #1141
Comments
As a part of this task we should also unify all |
Yep I'll sort that out once it's available (that's p4 too right?). For now I've just extended the multi-targeting while I'm playing with it locally. |
Hopefully yes, we just need to wait until the |
- Update to .NET 8 SDK. - Add `net8.0` TFM. - Bump packages to .NET 8 versions where relevant. - Remove `Microsoft.CodeAnalysis.NetAnalyzers`. Relates to #1141.
@martincostello I came across this post: https://devblogs.microsoft.com/dotnet/package-validation/ I think it's something we can do for V8 too! ;) |
Yep it would be good to add that too - I already use it in a number of my OSS projects. We should be able to enable it separate from the .NET 8 upgrade. |
Add NuGet package validation analysers. See App-vNext#1141 (comment).
Add NuGet package validation analysers. See #1141 (comment).
- Update to .NET 8 SDK. - Add `net8.0` TFM. - Bump packages to .NET 8 versions where relevant. - Remove `Microsoft.CodeAnalysis.NetAnalyzers`. Relates to #1141.
- Update to .NET 8 SDK. - Add `net8.0` TFM. - Bump packages to .NET 8 versions where relevant. - Remove `Microsoft.CodeAnalysis.NetAnalyzers`. Relates to #1141.
- Update to .NET 8 SDK. - Add `net8.0` TFM. - Bump packages to .NET 8 versions where relevant. - Remove `Microsoft.CodeAnalysis.NetAnalyzers`. Relates to #1141.
This issue is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further updates are made. |
Completed by #1144. |
Add a build configuration to validate in CI that Polly v8 works as expected with .NET 8 with a
net8.0
TFM using the prerelease packages.Once preview 4 is available, remove the internal
TimeProvider
copy and use the version shipping in a NuGet package instead.Once .NET 8 ships as stable in November, we can then roll
net8.0
into the main build setup and ship a package that explicitly supports it.The text was updated successfully, but these errors were encountered: