These are the customer-reported issues addressed in 15.7.2:

• With 15.7, users installing an extension on the command line with a nested extension may see an error installing. This has been addressed in the 15.7.2 servicing release.
• Anaconda fails to uninstall during upgrade and issues warning (Error 87).
• The SSDT 15.6.0 Installer configuration registry key could not be opened..
• Editor performance Issues when editing JavaScript.
• The Code Coverage functionality in Visual Studio 2017 ignores async methods.
• Missing atls.lib in arm/arm64 after update.
• Test Explorer no longer greys out the previously run unit tests.
• Version 15.7.1 debugs .aspx App in a new Chrome instance even if JavaScript debugging is disabled.
• 15.7 compiler fails with Folly.
• ASP project keeps running after closing the web page.
• Chrome Debugger not working and shows an error message, however, the debugger buttons stay active. .
• Rename Python from Rename on the Refactor menu no longer works.
• Visual Studio Installer doesn't work correctly in low disk space conditions.
• Debugger links to browser when previously not set.
• Problems with template argument deduction for class templates.
• C++ constexpr string_view == fails to compile.
• A regression in Type Providers which use native resources (e.g., FSharp.Data.TypeProviders) has been fixed.
• You can now add files to F# ASP.NET Core projects from the UI.
• Listening to Microsoft-Extensions-Logging causes VS diagnostic events window to disconnect with an error message has been fixed in Service Fabric Tools. 

Blazing into Summer 2.0: What’s New in Blazor in .NET 6?  

Burke learns Blazor by porting a Vue.js app to Blazor

This summer, Burke and Jon are porting theurlist.com to Blazor - a real world JavaScript application written in Vue.js. Join them each week as they use Visual Studio, Visual Studio Code and GitHub Copilot to rebuild this app and try to tackle every frontend issue you might encounter along the way.
 

Here’s what’s new in this release for ASP.NET Core:

• New component tag helper
• Prevent default actions for events in Blazor apps
• Stop event propagation in Blazor apps
• Validation of nested models in Blazor forms
• Detailed errors during Blazor app development 

In this course, we're going to be covering the fundamentals of Angular 2 to get you up & running as fast as possible. 

Have you ever found a bug in your code and wanted to pause code execution to inspect the problem? If you are a developer, there’s a strong chance you have experienced or will experience this issue many, many times. While the short and sweet answer to this problem is to use a breakpoint, the longer answer is that Visual Studio actually provides multiple kinds of breakpoints and methods that let you pause your code depending on the context! Based on the different scenarios you may experience while debugging, here are some of the various ways to pause your code and set or manage a breakpoint in Visual Studio 2017 

When you publish your Blazor Wasm app, this package pre-renders and saves the app as static HTML files in your public folder.  

Here’s what’s new in this release:

• Azure Active Directory authentication with Microsoft.Identity.Web
• CSS isolation for Blazor components
• Lazy loading in Blazor WebAssembly
• Updated Blazor WebAssembly globalization support
• New InputRadio Blazor component
• Set UI focus in Blazor apps
• Influencing the HTML head in Blazor apps
• IAsyncDisposable for Blazor components
• Control Blazor component instantiation
• Protected browser storage
• Model binding and validation with C# 9 record types
• Improvements to DynamicRouteValueTransformer 
• Auto refresh with dotnet watch 
• Console Logger Formatter
• JSON Console Logger