Validate v8 build with .NET 8
See original GitHub issueAdd 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.
Issue Analytics
- State:
- Created 5 months ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How to implement V8 into your .NET applications.
NET application. evaluate JavaScript input; expose a host type to the V8 ... Make sure to select the right package (ClearScript.V8).
Read more >Announcing .NET Community Toolkit 8.0! MVVM ...
We're happy to announce the official launch of the new .NET Community Toolkit, which is now live on NuGet with version 8.0.0!
Read more >8.0 Upgrade Guide — FluentValidation documentation
FluentValidation 8.0 is a major release that included several breaking changes. Please review this document before upgrading from FluentValidation 7.x to 8.
Read more >Referencing Google's V8 engine from a .NET app
It lets you create a V8 context from .NET and register CLI objects in it so you can manipulate them and call members...
Read more >What's new in the Twilio helper library for ASP.NET (v8.0.0
The RequestValidationHelper for Twilio.AspNet.Core now has an async method to validate HTTP requests: IsValidRequestAsync . (The async method ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hopefully yes, we just need to wait until the
System.Bcl.TimeProvider
package appears in nuget 😃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.