![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/09\/Blog_Featured_image_1280x720_ReSharper-2x.png\")
<\/figure>\n\n\n\nCode analysis performance improvements<\/h2>\n\n\n\n
ReSharper 2023.3 can now recognize and facilitate more scenarios where code analysis services can operate incrementally when interrupted by typing. This improvement is particularly beneficial for handling large files. The incremental approach ensures that only the necessary portions of the code are re-inspected when developers are still editing a file while the code analysis is ongoing. This speeds up continuous code analysis and conserves battery life on laptops.<\/p>\n\n\n\n
Reworked UX for the Extract local functions<\/em> refactoring<\/h2>\n\n\n\nWe’ve revamped the user experience for the Extract local function<\/em> refactoring. In the past, selecting a location for the new function from the list of available options was challenging, and it wasn’t clear what would be affected by that choice.<\/p>\n\n\n\nWith the updated UX, you’ll now see a preview of the new function’s signature directly in the code editor. This makes it easy to understand precisely where it will be inserted and how your choice will impact the introduced function. You can also see which variables will be transformed into parameters rather than closures, and which other functions will be relocated to allow calls at the new location.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/09\/Nnwwnlxp0D6rJ20GhszjXh7Mxkm9r0ihbjC8jIuSiqB9eOHgcM0FJcRq_DfiNn64WjdPK7VkLggjQ_zmw93VFinSAWM1mfDSIjaQy3hQA3CWNy9EU2JE0qk1b_EJSe3BZc2FglnsJTuNugKl9xYVDE4.gif\")
<\/figure>\n\n\n\nSupport for C# 12 interceptors<\/h2>\n\n\n\n
The latest version of C# has introduced an experimental feature called interceptors<\/a>. This feature leverages the new [InterceptsLocation] attribute, which enables you to intercept and redirect specific method calls within your application to an interceptor instead of the original method. This can be used for optimization, as you\u2019ll be able to fine-tune the interceptor method along with its exact arguments for a particular call site at compile time. <\/p>\n\n\n\nHowever, some source generators may override certain calls in your program and replace them with their own code.<\/p>\n\n\n\n
ReSharper 2023.3 will alert you to an intercepted call with an inlay hint icon, which can take you to the interceptor with a single Ctrl<\/kbd>+Click<\/kbd>. It’s also now possible to navigate back from the [InterceptsLocation]<\/code> attribute to the exact code position it intercepts. The same navigation actions are also available from the Alt<\/kbd>+Enter<\/kbd> menu.<\/p>\n\n\n\nYou might want to exclude certain generators from adding visual noise to the editor. For instance, you may not be interested in the latest ASP.NET Core being able to generate interceptors to optimize your .MapGet calls<\/a>. To prevent calls intercepted by a particular framework from being displayed, you can add the fully qualified name of the generator responsible for producing interceptor methods to the exclusion list in ReSharper\u2019s settings. Alternatively, you can also do so with Alt<\/kbd>+Enter<\/kbd> and context menus available directly from the inlay hint indicating the intercepted call. This means you don’t need to type the full name of the generator, or even know it beforehand to configure this behavior.<\/p>\n\n\n\nReworked integration of ReSharper and Visual Studio Quick Actions<\/h2>\n\n\n\n
Visual Studio and ReSharper\u2019s quick actions can complement each-other well when used discerningly. With ReSharper 2023.3 you can easily leverage the power of both systems. You can now tweak the settings to either use ReSharper\u2019s quick actions exclusively, display suggestion icons for both, or invoke all quick actions from a single access point \u2013 the ReSharper bulb menu. <\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/11\/image-9.png\")
<\/figure>\n\n\n\nWe\u2019ve also optimized Visual Studio\u2019s Quick Actions retrieval, improving the performance.<\/p>\n\n\n\n
New code formatting engine for Razor<\/h2>\n\n\n\n
ReSharper 2023.3 introduces a new formatting engine for Razor. It\u2019s compatible with the current ReSharper’s C# formatter, thus supporting C# language constructs introduced in recent years and most of ReSharper’s new formatting options for C#. The new formatter also operates faster and is expected to have fewer issues. However, it does modify the default formatting for some code. Therefore, we have introduced an option to revert to the old formatting engine for Razor. You can find it in ReSharper\u2019s Options under Code Editing | Razor | <\/em>Code Style.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2023\/11\/image-10.png\")
<\/figure>\n\n\n\nImproved support for projects that use StyleCop.Analyzers code style inspections<\/h2>\n\n\n\n
StyleCop.Analyzers<\/code> configuration files are now detected automatically in the projects where they are enabled, and StyleCop-related defaults are now provided even when no config files are present.<\/p>\n\n\n\nFile header templating overhaul<\/h2>\n\n\n\n
Arbitrary file header variables can now be configured in the file header settings page<\/a>. Also, there is now support for the StyleCop.Analyzers external file header templating. The Update file header<\/em> cleanup stage<\/a> should now correctly use it when the StyleCop.Analyzers are configured for the project that the cleaned up file belongs to.<\/p>\n\n\n\n\u0421++ updates<\/h2>\n\n\n\n
The EAP 6 build brings updates for HLSL support, code completion inside inactive preprocessor branches, a new inlay hint for forwarding references, and other updates. <\/p>\n\n\n\n
For more information, please check out this <\/a>dedicated<\/a> blog post<\/a>. <\/p>\n\n\n\nNew inspections for identifying vulnerable API usages<\/h2>\n\n\n\n
ReSharper 2023.3 brings a new security inspection feature designed to make published vulnerabilities more apparent and easier to understand.<\/p>\n\n\n\n
The new inspections identify vulnerable NuGet packages in your project and highlight instances where vulnerable methods from these libraries are used in your code. If a vulnerability is detected, the system highlights the problematic code and offers quick actions to remedy it. These actions include recommending an update to a newer version of the package and offering in-depth information about the detected vulnerabilities.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/09\/nIJzoxcXbnZpii5rE0wSNdQL_E4X_atGOKdQJzbcEANQrv9fKcyFiKhtwGx-HLNMfS4BQPioqq8qCC1S_K90AI-YS3Ma84TtGS4N_snTwFq6-lpCduDf826F5U6iwrFI6oASNS5xOQJ5MDA2dIMIobU.png\")
<\/figure>\n\n\n\nThat\u2019s it for now! For the full list of changes included in this build, please go to our issue tracker<\/a>. <\/p>\n\n\n\n
With the updated UX, you’ll now see a preview of the new function’s signature directly in the code editor. This makes it easy to understand precisely where it will be inserted and how your choice will impact the introduced function. You can also see which variables will be transformed into parameters rather than closures, and which other functions will be relocated to allow calls at the new location.<\/p>\n\n\n\n The latest version of C# has introduced an experimental feature called interceptors<\/a>. This feature leverages the new [InterceptsLocation] attribute, which enables you to intercept and redirect specific method calls within your application to an interceptor instead of the original method. This can be used for optimization, as you\u2019ll be able to fine-tune the interceptor method along with its exact arguments for a particular call site at compile time. <\/p>\n\n\n\n However, some source generators may override certain calls in your program and replace them with their own code.<\/p>\n\n\n\n ReSharper 2023.3 will alert you to an intercepted call with an inlay hint icon, which can take you to the interceptor with a single Ctrl<\/kbd>+Click<\/kbd>. It’s also now possible to navigate back from the You might want to exclude certain generators from adding visual noise to the editor. For instance, you may not be interested in the latest ASP.NET Core being able to generate interceptors to optimize your .MapGet calls<\/a>. To prevent calls intercepted by a particular framework from being displayed, you can add the fully qualified name of the generator responsible for producing interceptor methods to the exclusion list in ReSharper\u2019s settings. Alternatively, you can also do so with Alt<\/kbd>+Enter<\/kbd> and context menus available directly from the inlay hint indicating the intercepted call. This means you don’t need to type the full name of the generator, or even know it beforehand to configure this behavior.<\/p>\n\n\n\n Visual Studio and ReSharper\u2019s quick actions can complement each-other well when used discerningly. With ReSharper 2023.3 you can easily leverage the power of both systems. You can now tweak the settings to either use ReSharper\u2019s quick actions exclusively, display suggestion icons for both, or invoke all quick actions from a single access point \u2013 the ReSharper bulb menu. <\/p>\n\n\n\n We\u2019ve also optimized Visual Studio\u2019s Quick Actions retrieval, improving the performance.<\/p>\n\n\n\n ReSharper 2023.3 introduces a new formatting engine for Razor. It\u2019s compatible with the current ReSharper’s C# formatter, thus supporting C# language constructs introduced in recent years and most of ReSharper’s new formatting options for C#. The new formatter also operates faster and is expected to have fewer issues. However, it does modify the default formatting for some code. Therefore, we have introduced an option to revert to the old formatting engine for Razor. You can find it in ReSharper\u2019s Options under Code Editing | Razor | <\/em>Code Style.<\/p>\n\n\n\n Arbitrary file header variables can now be configured in the file header settings page<\/a>. Also, there is now support for the StyleCop.Analyzers external file header templating. The Update file header<\/em> cleanup stage<\/a> should now correctly use it when the StyleCop.Analyzers are configured for the project that the cleaned up file belongs to.<\/p>\n\n\n\n The EAP 6 build brings updates for HLSL support, code completion inside inactive preprocessor branches, a new inlay hint for forwarding references, and other updates. <\/p>\n\n\n\n For more information, please check out this <\/a>dedicated<\/a> blog post<\/a>. <\/p>\n\n\n\n ReSharper 2023.3 brings a new security inspection feature designed to make published vulnerabilities more apparent and easier to understand.<\/p>\n\n\n\n The new inspections identify vulnerable NuGet packages in your project and highlight instances where vulnerable methods from these libraries are used in your code. If a vulnerability is detected, the system highlights the problematic code and offers quick actions to remedy it. These actions include recommending an update to a newer version of the package and offering in-depth information about the detected vulnerabilities.<\/p>\n\n\n\n That\u2019s it for now! For the full list of changes included in this build, please go to our issue tracker<\/a>. <\/p>\n\n\n\n<\/figure>\n\n\n\nSupport for C# 12 interceptors<\/h2>\n\n\n\n
[InterceptsLocation]<\/code> attribute to the exact code position it intercepts. The same navigation actions are also available from the Alt<\/kbd>+Enter<\/kbd> menu.<\/p>\n\n\n\nReworked integration of ReSharper and Visual Studio Quick Actions<\/h2>\n\n\n\n
<\/figure>\n\n\n\nNew code formatting engine for Razor<\/h2>\n\n\n\n
<\/figure>\n\n\n\nImproved support for projects that use StyleCop.Analyzers code style inspections<\/h2>\n\n\n\n
StyleCop.Analyzers<\/code> configuration files are now detected automatically in the projects where they are enabled, and StyleCop-related defaults are now provided even when no config files are present.<\/p>\n\n\n\nFile header templating overhaul<\/h2>\n\n\n\n
\u0421++ updates<\/h2>\n\n\n\n
New inspections for identifying vulnerable API usages<\/h2>\n\n\n\n
<\/figure>\n\n\n\n