In Visual Studio 2022, we are continuing to add new C++ sanitization features to help you write reliable and secure C++ code. In Preview 4, there’s a big update for the Blazor and Razor editors, addressing the issues in Preview 3 that we’re reported to us – thank you! Along with fixes, there are new capabilities for hot reload in ASP.NET Core – including hot reload on file save and applying changes to CSS files live! This can make debugging code in common paths (like a game loop or a utility API) much easier as a breakpoint in those functions can be configured to enable only if the function is invoked from a specific part of your application. From updates to the new external source feature, which make it easier to load symbols for libraries outside your project, to new features like dependent breakpoints, for configuring additional breakpoints after another breakpoint is first hit. From updates to the attach to process dialog where you can now select processes by using a window picker.
The Preview 4 release also has a number of improvements for debugging. The performance team is planning a blog dedicated to performance improvements, so stay tuned. Other scenarios where we’ve improved performance include C++ IntelliSense performance improvements with a ~12% speedup for semantic colorization, optimizations to symbol database processing, and an almost 2x speedup for expanding C++ items in the solution explorer. For example, find in files is now as much as 3x faster when searching large solutions such as Orchard Core. In Preview 4, we’ve focused on improving the performance of several key features. In previous blog posts, we’ve talked about how our move to 64bit has led to significant improvements in scalability.
A focus area for Visual Studio 2022 is improving the scalability and performance of Visual Studio.
0 kommentar(er)
