The Bootstrap team has a comprehensive guide for migrating to Bootstrap v4. However, there is a very nifty tool from the community, that allows you to drop in a piece of code and convert it to the Bootstrap v4 equivalent. 

• Updated the version of .NET that the debugger uses for running its own C# code to .NET 5 

This guest blog post is the first of a 3-part series written by Windows MVP Jani Nevalainen. 

• Custom Project Template Not Found
• msvsmon.exe crashes when hitting breakpoint in native C++ code
• Search for a folder in solution explorer, then click home or the X in the search box. The view is reset.
• External Tools argument current line is always zero.
• Can't create v3 Function project.
• Access violation reading location 0xFFFFFFFFFFFFFFFF. after updating to VS 2019 Update 16.4.3
• Cannot create function app under 16.4
• MSVC2019 generates AVX-512 instruction in AVX/AVX2 mode
• Bad code generation with rsqrtss (register clobber)
• Visual Studio 2019 Debugger crashes when viewing FastLink callstack.
• C#: Fixed a crash when an attribute constructor is decorated with itself and Nullable Reference Types is enabled.
• Fixed an optimization-analysis bug where we lose track of alias information for arrays of indeterminate length (declared as extern int a[]) when we unroll loops, leading to possible incorrect dead-store removal. 

As a refresher, the Windows code base is approximately 3.5M files and, when checked in to a Git repo, results in a repo of about 300GB .  

The conclusion of the analysis:
C# Wasm AOT still has a long way to become a general and performant client side web programming platform. Note: The usage of the Uno.Wasm.Bootstrap toolchain may have affected the performance of some of the benchmarks. Thus, this analysis should not be regarded as a benchmark of the finalized product. However, note that the Uno platform is using ".NET 6 WebAssembly Mixed mode AOT/Interpreter" (source). 

C# 9.0 is taking shape, and I’d like to share our thinking on some of the major features we’re adding to this next version of the language. 

HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Most likely causes:

    A default document is not configured for the requested URL, and directory browsing is not enabled on the server.

Things you can try:

    If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists.
    Enable directory browsing using IIS Manager.
        Open IIS Manager.
        In the Features view, double-click Directory Browsing.
        On the Directory Browsing page, in the Actions pane, click Enable.
    Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.

Detailed Error Information:
Module DirectoryListingModule
Notification ExecuteRequestHandler
Handler StaticFile
Error Code 0x00000000
Requested URL http://localhost:80/3724/
Physical Path C:\inetpub\wwwroot\3724\
Logon Method Anonymous
Logon User Anonymous