𝗖# 𝗶𝗻 𝗩𝗦 𝗖𝗼𝗱𝗲 𝗮𝗹𝘄𝗮𝘆𝘀 𝗳𝗲𝗹𝘁 𝗯𝗿𝗼𝗸𝗲𝗻. In March, this finally changed 👇 What's the problem with C# in VS Code? You open your .NET solution in VS Code, Cursor, or another lightweight editor. You get basic syntax highlighting. Some IntelliSense. Maybe a few squiggly lines. But real productivity? That's been missing. Here is what I kept running into: • Weak code analysis that misses real issues • Limited refactoring support • Limited Solution Explorer • No reliable navigation to decompiled sources • No built-in unit test runner • AI-generated code with no quality layer on top For years, the only real options were: ❌ Use a full IDE like Visual Studio or Rider ❌ Piece together multiple VS Code extensions and hope they work This changed in March. JetBrains officially released 𝗥𝗲𝗦𝗵𝗮𝗿𝗽𝗲𝗿 for VS Code, Cursor, and Google Antigravity: jetbrains.com/resharper/?pro… This is the same ReSharper engine that millions of developers have trusted in Visual Studio for 20+ years, now running in VS Code, Cursor, and Google Antigravity. 𝗔𝗻𝗱 𝗵𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝗯𝗲𝘀𝘁 𝗽𝗮𝗿𝘁: 𝗶𝘁'𝘀 𝗙𝗥𝗘𝗘 𝗳𝗼𝗿 𝗻𝗼𝗻-𝗰𝗼𝗺𝗺𝗲𝗿𝗰𝗶𝗮𝗹 𝘂𝘀𝗲, 𝘀𝘁𝘂𝗱𝘆𝗶𝗻𝗴, 𝗮𝗻𝗱 𝗵𝗼𝗯𝗯𝘆 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀. Here is what made a real difference for me: 1️⃣ Professional-grade code analysis ↳ Real-time inspections and quick-fixes for C#, Razor, Blazor, and XAML. It catches issues that basic extensions completely miss. 2️⃣ Smart coding assistance ↳ Context-aware completion, auto-imports, live templates, and inline documentation that go way beyond what a standard editor offers. 3️⃣ Solution Explorer inside VS Code ↳ A central hub for managing files, folders, NuGet packages, and projects across your entire solution. Just like in Rider or Visual Studio. 4️⃣ Refactoring you can trust ↳ Rename works across your whole solution while safely handling conflicts and references. No more search-and-replace guessing. 5️⃣ Fast navigation to any source ↳ Jump to symbols, usages, files, and types. When source code is not available, ReSharper decompiles assemblies and takes you directly to the declaration. 6️⃣ Built-in unit testing ↳ Run and manage tests for NUnit, xUnit .net, and MSTest directly in your editor with easy navigation to failing tests. The next major area of focus for ReSharper for VS Code is debugging support. JetBrains is actively working on support for launching debugging sessions and attaching to processes in .NET and .NET Framework applications. 👉 You can install ReSharper in the Extensions view of your editor (VS Code, Cursor, and Google Antigravity) —— Many thanks to @jetbrains for sponsoring this post

𝗔 𝗻𝗲𝘄 𝗴𝗼𝘁𝗼 𝗶𝘀 𝗰𝗼𝗺𝗶𝗻𝗴 𝘁𝗼 𝗖# 𝟭𝟱 And you will use it 👇 Sounds scary, right? But this one is different. The official champion proposal for C# 15 introduces 𝗹𝗮𝗯𝗲𝗹𝗲𝗱 𝗯𝗿𝗲𝗮𝗸 𝗮𝗻𝗱 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲 statements. It solves a problem we all hit with nested loops. And we usually solve it badly: ❌ Use goto with weird labels at the bottom of loops. ❌ Use flags that leak state and hide intent. Both make code harder to read and maintain. Now imagine this instead. → You name the loop you want to exit. → Then you say exactly what you mean. "Break outer loop." "Continue outer loop." And yes, other languages already do this: → Java, Kotlin, Rust, Go, Swift. C# is finally catching up. This feature has been requested for years. It is now officially championed. Which means it is very likely coming. And once it does, you will use it. Not because it is fancy. But because it is simply better. Personally, I like this idea. What do you think about this C# feature? 📌 Want to be the first who learns about new features in C# 15 and .NET 11? Join 22,350+ developers reading my .NET Newsletter: antondevtips.com/?utm_source… —— P.S.: I have put the link to the official proposal in my pinned comment ♻️ Repost to help others learn about the new C# 15 feature ➕ Follow me ( @AntonMartyniuk ) to improve your .NET and Architecture Skills