You can say the entire team here at JetBrains were really excited when we read that Visual Studio 2022 will become a 64-bit process. Memory will become cramped in larger solutions, which means the garbage collector needs to kick in more often, and throughput will suffer. So even if you have a monster development machine with 128 processors, SSD drives and 1TB of memory, Visual Studio will only ever use ~4GB of memory, (roughly 2.5GB of managed memory). And Visual Studio itself has added extra memory demands in recent versions, with the new SDK-style project format requiring quite some additional memory. NET runtime, ReSharper, and Visual Studio’s own features, including the WPF based UI, source control, and any other installed plugins. This memory space is shared between your project files, the. – run inside the Visual Studio process.īecause Visual Studio is a 32-bit process, it can only use between 2.5 GB and 4 GB of memory. In this blog post, let’s look at why 64-bit matters, and what we believe it will mean for ReSharper.Īll of ReSharper’s features – navigation, code completion, inspections, quick fixes and refactorings, unit testing, diagramming, find usages, etc. Our own Rider IDE has been 64-bit since 2017, and it’s great to see Visual Studio finally doing this too. The announcement from Microsoft also reveals that Visual Studio will be 64-bit.

Update (December 8, 2021): ReSharper 2021.3, with support for Visual Studio 2022, is now available for download. And of course, we will make sure that ReSharper is available for it to help you write better code. Good news! Microsoft has announced a new version of Visual Studio 2022.

Visual studio code 2022