Regarding the docs - the general statement is still correct but it's definitely outdated in some places such as The dependency should be set to for ReSharper 9.1, and for ReSharper 9.0. I had to manually use the "pack" command to see the resulting NuGet package. I suppose this is intended considering there is the buildPlugin.ps1 script? But it doesn't produce NuGet package either. I'm a bit confused the csproj doesn't set to produce NuGet package on build. We’re eager to hear how it works for you.I've checked 0.9.0 and it's building without any issues, however it seems to target new ReSharper EAP only? The resulting nuspec file (in nuget package) contains:
Resharper 9 eap code#
You can find them in Tools | Options | Decompiler | Code style and formatting. We’ve updated the formatter for decompiled code with a set of options to control how the code is presented. The options to pin tabs and to color code them can be disabled in Tools | Options | Environment | Tabs. Additionally, the color of a tab now indicates the type of code you will see – green represents a metadata view and brown stands for sources from symbol files. When working with several tabs at once, you can now pin them. Please refer to this ReSharper C++ blog post for a detailed account of all the changes. We’ve also added coroutine-specific postfix templates and improved the configurability of aggregate initialization hints. There is also a new inspection that detects template arguments that can be deduced by the language, with a quick-fix to remove redundant arguments. We’ve introduced support for several new C++ features from the latest standards: class types in non-type template parameters, C++20 class template argument deduction rules, and noexcept as a part of the function type. We’ve also sped up typing in any large files where ReSharper’s analyzers are working. We’ve sped up typing in Razor files inside large solutions ( RSRP-481771).
Resharper 9 eap windows#
We’ve got warnings from Windows Defender under control ( RSRP-481078).
Resharper 9 eap full#
Stay tuned, as we’ll publish the full details when they’re ready to ship.ĮAP1 also includes a bunch of notable bug fixes: In our perpetual quest for performance, we’re working on a set of metrics that should help us analyze performance lags and gather statistics. If you frequently use RegEx, C# in Razor, or other injected languages, you’ll probably appreciate the extend / shrink selection feature, which now works in injects as well. When you invoke Copy Fully-qualified name with ReSharper | Edit or Ctrl+Shift+A, ReSharper not only does the copying, it also opens a context menu where you can choose from a variety of formats. One more useful action we’ve added is for copying GitHub links via the ‘Copy FQN’ feature. We’ve upgraded our support for QUnit to version 2.14.0. We’ve implemented performance improvements for JavaScript and TypeScript unit testing. We’ve added settings to wrap before the assignment operator and to outdent label statements, and we’ve fixed an issue affecting indentation in multiline interpolated string inserts. We continue to add support for C# 9 features, and this time we’ve added settings for a space before and within target-typed new() parentheses. This can be useful if you are doing something with the file itself, like copying it or copying the path inside the repository, or if you prefer to view the file’s VCS history using Git extensions for Windows Explorer.Īs usual, there are some new formatting options and improvements. You’ll find it in Navigate | Navigate to menu or by pressing Ctrl+Shift+A and typing its name. You now have a new navigation action – Navigate to Windows Explorer. ReSharper now suggests using the range operator instead of Slice and Substring when doing so simplifies your code. There’s a new inspection that checks whether an auto-property can be replaced with a computed property, along with a quick-fix to make the replacement. Let the 2021.1 EAP begin! We’ve just published ReSharper 2021.1 EAP1, let’s see what’s inside.
0 kommentar(er)
