Microsoft released Visual Studio 2022 17.8 Preview 3. This version mainly addresses community feedback and resolves almost 100 tickets. Additionally, there are some new features: an “Update on Close” option, Unreal Engine macro specifier suggestions, structured diagnostics, and an upgrade in SQL Server Data Tools.
An overlay now appears on the Visual Studio on the VS taskbar icon to inform when IDE will update. The icon will appear when an update is available, and a user has enabled the “Update on Close” option. Once a user closes Visual Studio, an update will start, and the icon will disappear.
Visual Studio 2022 17.8 Preview 3 contains some improvements within C++ Game Dev. Microsoft developers added Unreal Engine macro specifiers suggested in the member list. Thanks to that, it is easier to understand and use them. This feature allows quick access to important information about macro specifiers without having to leave the IDE.
Unreal Engine macro specifiers suggested (Source: Microsoft blog)
Considering that C++ compiler errors can be long and inconvenient, Microsoft has created a new Problem Details window that allows orderly navigation through compiler errors. The Problem Details window can be opened by clicking the Details icon next to an entry in the Error List.
Problem Details window (Source: Microsoft blog)
SQL Server Data Tools has upgraded from Microsoft.Data.SQLClient 3.0 to 5.0. The new version has support for TDS 8.0, support for specifying Server SPN and Failover Server SPN on the connection. Furthermore, SSDT has two new fields in the Connect Page: Encrypt and Trust Server Certificate. This specifies the Encryption type and the requirements for a Trust Server Certificate. By default, the Encrypt is set as true or mandatory.
SSDT window (Source: Microsoft blog)
Below the official release post appeared different comments and questions. Among others, the community asked why the welcome page disappeared. Erik Hennerfors wrote:
I have to agree the “Welcome page” was way better than the old “Start window”. It's so sad to see this being reverted, at least give us the choice!
Apart from that, users mentioned some bugs within Blazor applications. Leslie Richardson, a Microsoft program manager, answered that they realised that it is impossible to keep fixing these Razor and Blazor issues unless they change the compiler and tooling architecture. In addition, they created a ticket on the Developer Community where updates about the Razor editor appear.