Our release for ReSharper and Rider 2024.2 is just around the corner, and we have lots of exciting features shipping for the new C# 13 and current C# and VB.NET! Since there are so many, we will split them into multiple blog posts. So make sure to check those posts out as well!<\/p>\n\n\n\n
In this series, we will cover features around:<\/p>\n\n\n\n
Make sure to download the latest version of ReSharper or Rider to follow along:<\/p>\n\n\n
With C# 13, we are getting a new control sequence for the ESC character<\/a>. Previously, you had to use the hexadecimal escape sequence In 2024.2, we are adding support for the new escape character and allowing you to easily migrate your codebase. As with some other features in this blog post, we’ve been looking more closely at what other areas in our language support could be improved along the way. So with the To enhance the handling of escape sequences in C#, we’ve added a whole set of context actions that allow you to switch between different representations, such as plain text, ASCII text (where non-ASCII characters are replaced with escape sequences), or a sequence of Those actions are also useful for uncovering the code points of individual characters. For example, the following two string literals are rendered equally in the editor, but are actually represented by different code sequences:<\/p>\n\n\n\n Furthermore, we are now warning about ordinary As you hack your way through codebases, it’s possible that you end up with small to large code duplications. Wouldn’t it be nice if your IDE told you about them?<\/p>\n\n\n In 2024.2, we are introducing a new code inspection Extract Common Code<\/em> to analyze code inside branching constructs, more specifically More importantly, the inspection can also help you catch bugs! Often the equivalent code in branching constructs is the result of copy & pasting code around. The inspection will bring that up to your attention, hinting that the code was supposed to be different. For an easy win, you can hit While we recently investigated support for collection expressions<\/a>, we’ve also revisited related language features such as the With 2024.2, we are introducing the Add\/Remove ‘params’ modifier and update usages<\/em> context actions for C# and VB.NET to improve your API ergonomics and update all usages in one go:<\/p>\n\n\n\n Since C# 7, you can use In 2024.2, we decided to finally address this new syntax in our code completion \u2013 including smart naming suggestions! The quickest way for you is to use the In some cases, the Give it a go with the latest ReSharper 2024.2 <\/a>and Rider 2024.2<\/a>, and let us know if you have any questions or suggestions in the comments section below.<\/p>\n","protected":false},"author":553,"featured_media":500154,"comment_status":"closed","ping_status":"closed","template":"","categories":[4992,1401,3990,4140],"tags":[158,211,2015,603,756,46,1978,1989],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/dotnet\/499891"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/dotnet"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/types\/dotnet"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/users\/553"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/comments?post=499891"}],"version-history":[{"count":9,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/dotnet\/499891\/revisions"}],"predecessor-version":[{"id":508373,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/dotnet\/499891\/revisions\/508373"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/media\/500154"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/media?parent=499891"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/categories?post=499891"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/tags?post=499891"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/cross-post-tag?post=499891"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\\0x1B<\/code> to express this character, while now, you can simply use \\e<\/code>. This is especially attractive for virtual terminal sequences<\/a>, which you can use to apply text formatting<\/a> to console applications (including colored, bold, and blinking text).<\/p>\n\n\n\n\\e<\/code> support, we generalized the simplification inspection to identify other escaping shortcuts, such as \\t<\/code> or \\n<\/code>, to keep your string literals in the most \u201ccanonical\u201d form:<\/p>\n\n\n\n\\u<\/code> and \\x<\/code> Unicode codes. These actions can be applied to escape sequences, entire string literals, or selected character sequences. For instance, if you want to include a non-ASCII symbol in a string literal while maintaining ASCII encoding in the source code, you can use the new Convert to ASCII text<\/em> action:<\/p>\n\n\n\n\\x<\/code> escape sequences followed by ASCII letters. Unlike in other programming languages, the \\x<\/code> escaping sequence in C# allows a variable number of hexadecimal characters to follow the prefix (only \\u<\/code> requires exactly 4 hex numbers). That means you could accidentally attach characters to the sequence. The new Avoid mixing variable-length escape sequences and text<\/em> inspection helps you spot such cases:<\/p>\n\n\n\nExtract Common Code<\/h2>\n\n\n\n
var<\/span> sb<\/span> =<\/span> new<\/span> StringBuilder<\/span>();\r\nvar<\/span> version<\/span> =<\/span> NuGetVersion<\/span>.<\/span>Parse<\/span>(\"1.3.3.7\"<\/span>).<\/span>Version<\/span>;\r\n\r\nif<\/span> (version<\/span>.<\/span>Major<\/span> >=<\/span> 5<\/span>)\r\n{\r\n sb<\/span>.<\/span>Append<\/span>(\"?view=net-\"<\/span>);\r\n \/\/ duplicated from here<\/span>\r\n sb<\/span>.<\/span>Append<\/span>(version<\/span>.<\/span>Major<\/span>).<\/span>Append<\/span>(\".\"<\/span>).<\/span>Append<\/span>(version<\/span>.<\/span>Minor<\/span>);\r\n}\r\nelse<\/span>\r\n{\r\n sb<\/span>.<\/span>Append<\/span>(\"?view=netcore-\"<\/span>);\r\n \/\/ duplicated from here<\/span>\r\n sb<\/span>.<\/span>Append<\/span>(version<\/span>.<\/span>Major<\/span>).<\/span>Append<\/span>(\".\"<\/span>).<\/span>Append<\/span>(version<\/span>.<\/span>Minor<\/span>);\r\n}<\/code><\/pre>\n if<\/code> and switch<\/code> statements. This new inspection can detect same code in the beginning and ending of all branching execution paths:<\/p>\n\n\n\nAlt-Enter<\/code> and look for the Run Inspection By Name<\/em> action<\/a> and find all occurrences in your codebase.<\/p>\n\n\n\nParams Modifier Refactoring<\/h2>\n\n\n\n
params<\/code> modifier<\/a>, which has been available in C# from day 1. When writing an API, you may not immediately know that you can take advantage of the params<\/code> modifier. On the other hand, once you know it, plenty of code may already have been written. A short example:<\/p>\n\n\n void<\/span> M<\/span>(string<\/span> text<\/span>, Type<\/span>[] types<\/span>)\r\n{\r\n M<\/span>(\"plain array\"<\/span>, new<\/span>[] { typeof<\/span>(int<\/span>) });\r\n M<\/span>(\"collection expression\"<\/span>, [ typeof<\/span>(int<\/span>) ]);\r\n}<\/code><\/pre>\n Out Variable Code Completion<\/h2>\n\n\n\n
out<\/code> variable declarations<\/a>, which significantly reduce ceremony when calling methods with out<\/code> parameters. Not only can you capture values right from the argument, but you can also discard them if only the method return value is of importance.<\/p>\n\n\n\novv<\/code> shorthand:<\/p>\n\n\n\nout var<\/code> argument must have an explicit type annotation to help with overload resolution. In this case, our code completion will provide you with all the possible types:<\/p>\n\n\n\nConclusion<\/h2>\n\n\n\n