Missing Blazor intellisense in VS2022? You may be running into this problem 

Visual Studio 2022 Preview 1 was released recently. While normally I hold off on talking about preview releases and other items that are going to change rapidly like .NET 6, I think it is important to know what VS2022 is all about so you know what to expect in the coming months. So in this video, we are going to see VS2022 in action, we will see what the new features are, and we will talk about what this means for VS2019. 

Top Issues Fixed in Visual Studio 2019 RC.1

• Visual Studio 2019 Preview 4 crash if closing undocked Window.
• Intellisense error: C++11 static constexpr member initialization causes "member may not be initialized".
• Start Page "Remove From List" stops working.
• $(VCIDEInstallDir) is an invalid path. Missing backslash in Microsoft.Cpp.Common.props.
• Visual Studio 2019 Preview 2.0+ crashes when opening soultion filter.
• Manage Extensions toolbar throws exception.
• Fixed rendering of the Import and Export Settings Wizard when running per-monitor aware
• Fixed sizing of the New Project Dialog when running per-monitor aware
• Made a set of visual refinements to the start window 

• DateTime.Now = Cannot provide the value: host value not found
• MSVC codegen error vector reverse_iterator x64 C++17 debug build
• C2440 error building atlenc.h with /permissive- in VS 16.4 Preview 1
• Last Visual Studio update broke NTLM authentication on Android (seems like new version of Momo would be a reason)
• Visual Studio 16.3.1 fails at compiling template code (e.g. from Basler Pylon SDK)
• Using TypeScript 3.7 for IntelliSense
• XCode 11.3 is too new all of a sudden after update to 8.4
• You uploaded an APK or Android App Bundle with invalid or missing signing information for some of its files. You need to create a valid signed APK or Android App Bundle.
• Unable to Run UWP project
• JavaScript IntelliSense not working after update 16.4.1
• Xib : Xcode is to new(rendering problem when using custom components)
• Storyboard error: 'Xcode is too new'
• Stability improvements for debugging watchOS applications.
• Adds Xcode 11.3 SDK support.
• Fixed crash when fstack-protector-strong flag is enabled.
• Fixed some inconsistent behavior with Debugger.

Security Advisory Notice

CVE-2020-0602 ASP.NET Core Denial of Service Vulnerability
CVE-2020-0603 ASP.NET Core Remote Code Execution Vulnerability
CVE-2020-0605 .NET Core Remote Code Execution Vulnerability
CVE-2020-0606 .NET Core Remote Code Execution Vulnerability

Here’s what’s new in this preview release:

• Improved Blazor accessibility
• Required Blazor component parameters
• Efficient byte array transfers for JavaScript interop
• Optional parameters for view component tag helpers
• Angular template updated to Angular 12
• OpenAPI support for minimal APIs
• Inject services into minimal APIs without [FromServices] attribute
• Configure the accept socket for Kestrel
• IHttpActivityFeature
• Long running activity tag for SignalR connections
• WebSocket compression
• SignalR WebSockets TestServer support
• New OnCheckSlidingExpiration event for controlling cookie renewal
• ClientCertificateMode.DelayCertificate 

Blazor Hybrid for Beginners
Join James Montemagno as he takes you on a journey of building your first Hybrid applications across iOS, Android, Mac, Windows, and Web with ASP.NET Core, Blazor, Blazor Hybrid, and .NET MAUI!  You will learn how to use Blazor Hybrid to blend desktop and mobile native client frameworks with .NET and Blazor.
In a Blazor Hybrid app, Razor components run natively on the device. Components render to an embedded Web View control through a local interop channel. Components don't run in the browser, and WebAssembly isn't involved. Razor components load and execute code quickly, and components have full access to the native capabilities of the device through the .NET platform. Component styles rendered in a Web View are platform dependent and may require you to account for rendering differences across platforms using custom stylesheets.
Blazor Hybrid support is built into the .NET Multi-platform App UI (.NET MAUI) framework. .NET MAUI includes the BlazorWebView control that permits rendering Razor components into an embedded Web View. By using .NET MAUI and Blazor together, you can reuse one set of web UI components across mobile, desktop, and web.
 

Welcome to this short introduction to Blazor! This new Microsoft framework uses a unique approach to leverage your existing C# and .NET skills to create single-page applications running in web browsers. The technology that makes this possible is called WebAssembly, an open standard supported directly by current browsers on desktop and mobile platforms. You write C# and Razor code instead of JavaScript, and the compiled app runs natively on the client.

Sample Source Code: https://github.com/DevExpress/blazor-training-samples  

With this newest Blazor release we’re pleased to announce that Blazor is now in official preview! Blazor is no longer experimental and we are committing to ship it as a supported web UI framework including support for running client-side in the browser on WebAssembly. 

These are the customer-reported issues addressed in 15.7.3:

• VS2017 compiler creates broken debug build using Qt framework and generates 'Invalid address specified to RtlValidateHeap' error.
• Incorrect code generation for matrix multiplication.
• VS 2017 Update 7: Git History Codelens only showing entries for the past 6 months.
• UWP projects reference multiple NetStandard 2.0 dlls after 15.7.1 upgrade.
• Building C++ code in VS 15.7 with /std:c++17 breaks binary compatibility for std::_Ptr_move_cat.
• Visual Studio 15.7 stuck when opening XAML files.
• CMake configuration fails and generates message "C++ IntelliSense information may be out of date, generate the CMake cache to refresh".
• Unable to start second process for debugging.
• After update to Visual Studio 15.7.1, some test programs fail in start-up due to reading access violation.
• Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.Binder.Convert'.
• Build fails after 15.7.0 update on older project using .NET 3.5 .
• Coloring, typing, tooltips and IntelliSense slow in F# in VS2017 editor.
• F# editing experience takes up to a minute for tooltips and dropdowns to display.
• Certain class member variable value are incorrectly read as zero.
• Attempt to open XAML file for the first time causes VS to sit with the "Opening the file ..." message for about 10 minutes before XAML file opens.
• Visual Studio slows down and freezes, creating work loss.
• The target "GetBuiltProjectOutputRecursive" does not exist in the project.
• Internal error with lambda C++17 after 15.7.1 update.
• UWP App is slow to return a stopped state in IDE.
• MSVC auto-vectorization produces incorrect code or incorrect results.
• Visual Studio closed debug a new instance project1, when a new debug new instance project2 has started.
• Latest update breaks "start without debugging" on multiple projects.
• UWP XAML is very very slow on open.
• XAML viewer freezes on 15.7.2 and 15.8.0 preview 1.1.
• Xamarin UI Test App project template missing.
• Xamarin project creation problem.
• Visual Studio crashes when creating new Mobile APP Xamarin.
• Unable to create Xamarin.Forms-Projects.
• Não consigo criar novos projetos Xamarin Forms - Can't create new projects Xamarin Forms.
• Blank project crash after update.