NET Core, we’ve been using the standard “vstest” runner.
#Resharper youtrack code#
We’ve always run your tests in an external process, so we can handle multiple target frameworks, as well as provide parallel execution, code coverage and so on. Unit testing – this release will bring a new unit test runner process.Better Blazor support – we’re aiming to improve the Blazor experience with ReSharper, with better integration with Razor components relating to references, navigation, and code completion.We’ll be starting work on supporting those features when they are closer to being stable. And we’ve also got C# 9 coming, with some very interesting proposals such as records, top level programs and more improvements to pattern matching. ReSharper already has great support for async streams but we’re aiming to provide even more features, in particular, enable await foreach to LINQ conversion. But we’re also looking at other C# 8 features such as async streams, which is a fairly complex topic, and provides many opportunities for inspections and helping you rewrite your code to take advantage of these new features. We’re continuing to improve support and features for nullable reference types, with extra inspections, quick fixes and context actions. C# 8 (and 9) – the C# language is always evolving, and ReSharper needs to evolve along with it.We already have interfaces to work with different versions of the Visual Studio text editor implementations which will help, but these interfaces were designed to work synchronously, in process, so it will take some work to make them properly asynchronous. In this release, we’ve already got the project and code models able to run out of process, and we’re now working on moving our text editor integration out of process too. We’re getting very close to having something to show, but there is still a lot to do. Out of process – we’re continuing to work on the delicate process of unpicking years of synchronous execution and API usage assumptions and replacing them with asynchronous out of process calls.With that disclaimer out of the way, let’s take a look at what’s coming! These are the broad areas we’re working on, and a list of our priorities, but things can change before release. NET.Īs ever, please be aware that this list is preliminary. We recently published the Rider 2020.2 roadmap, as well as the ReSharper C++ 2020.2 roadmap, and we’d now like to bring you up to speed with what we’ve got planned for ReSharper 2020.2 in.
0 kommentar(er)
