The release of Visual Studio 2022 17.4 started a few weeks ago. Because it includes.NET 7 and natively supports Arm64 in addition to Windows x64 and Mac architectures, this version is significant. It also has a tonne of other features like rollback and interaction with multiple repositories. Microsoft has now provided a complete list of all the significant performance enhancements in the most recent edition of its well-known integrated development environment.
To begin with, compared to version 17.3, Find and Replace in Files is now a staggering 3–4 times faster. Microsoft claims that it has achieved this by making little adjustments like Async saving and increasing cache and indexing. Microsoft’s test data shows that replacement procedures take 25 seconds on Visual Studio 2022 17.3 compared to 8 seconds on version 17.4 at the 95th percentile.
Additionally, indexing is now quicker for C++ projects as well. In large C++ projects, populating the source code index results in a 25–30% performance improvement.
Similar to this, branch switching now requires 80% fewer solution reloads. Furthermore, branch switching in Visual Studio 2022 17.4 requires about 10 seconds less time than it did in Visual Studio 2019, which required 16 seconds on the 95th percentile.
Meanwhile, the following table summarises the performance improvements for.NET configuration switch responsiveness:
| Improvements | 17.3 (seconds) | 17.4 (seconds) | Gain |
|---|---|---|---|
| Inheritance Margin | 51.1 | 26.6 | 47.90% |
| Errors | 60.3 | 27.8 | 53.90% |
| CodeLens | 128.3 | 38.2 | 70.20% |
| Background tasks | 219.2 | 89.9 | 58.90% |
When it comes to unit tests, Test Explorer ought to reveal tests across projects considerably more quickly. When Microsoft tested a solution with 150 projects and 300,000 tests, performance was double that of the prior release. Similar to how test runners made connections more quickly, test assemblies ran three times faster.
Finally, to ensure that the IDE is responsive and unaffected by the saving process, the majority of Save operations have been moved to a background thread. According to Microsoft, network shares, huge projects, and slow hard drives will show this benefit the most. You may provide Microsoft with feedback by filling out a survey or using this portal.
