The language continues to evolve, and we continue to keep up. This should see us ready for an alpha preview.Ĭ# 9 and 10. We’re also hard at work removing all usages of our "document" abstraction from the part of ReSharper that still needs to run in the Visual Studio frontend, which will allow us to properly separate the Visual Studio editor from ReSharper running in the background process. ReSharper has approximately 700 of these actions, and we’re nearly done migrating them all. These are the toolbar buttons, menu items and context menu items – UI elements which obviously need to integrate with Visual Studio, but now need to also work asynchronously in another process (we need to keep current ReSharper running in process, while we work on out of process). We’ve recently been migrating all ReSharper actions so they can run in this backend process. We can already run a bare bones instance of ReSharper out of process, with a project model, language parsing and analysis and more (which is quite a lot for “bare bones”). But we are making steady progress on a mammoth task. Yes, we’re still working on running ReSharper outside of the Visual Studio process, and yes, we’ve been talking about it for a very long time. Let’s dive in, and please, let us know your feedback! As ever, priorities can change and we might move things in and out of scope. As with the Rider post, this is a list of what we’re working on, what we hope and currently intend to ship with ReSharper 2021.1. We recently posted our roadmap for Rider 2021.1, so let’s take a look today at what’s brewing for ReSharper 2021.1, and the other dotUltimate tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |