

JetBrains ReSharper
5.1K posts

@resharper
Legendary Visual Studio extension for .NET and web developers. Made by @JetBrains. Also the backend for @JetBrainsRider, a cross-platform .NET IDE.




Do .NET developers still need Solution Explorer? For 24 years, the answer was obvious. Every major .NET tool included Solution Explorer. But in May, the C# Dev Kit extension removed it from VS Code. Microsoft explained that the file system is now the main source of truth, and modern formats like .slnx and SDK-style .csproj are designed for this. However, a repository tree and a solution structure are not always the same. Solution folders, linked files, projects outside the workspace, and file nesting are not visible in the file system. On the other hand, having one real tree means all your paths match Git and the CLI, and there is no solution graph to load. Rider and ReSharper for VS Code both include Solution Explorer, and we continue to invest in it. This is why we’re asking: Is Solution Explorer essential to your workflow? If it is, let us know. If not, and File Explorer is enough, we want to hear about that, too. Do you prefer solution-aware tools or a file-system-first approach? Share your thoughts in the comments here or on LinkedIn: linkedin.com/feed/update/ur…










Good news for performance hunters: the @dottrace integration in Visual Studio now works with @resharper 's Out-of-Process mode in 2026.2⚡ Profile right inside VS while ReSharper runs at its leanest and most responsive. Version 2026.2 is already available from our website.












You asked, and we delivered. Debugging was the #1 request from .NET devs. With ReSharper 2026.2, it's here, joining the inspections, refactorings, and Solution Explorer you already use in @code , @cursor_ai, and compatible editors. Why wait? Install and debug today. 🔗 jetbrains.blog/rs-vsc-debuggi…
