Blazor in .NET 6 enables building even more powerful and flexible web UI components. In this session we'll look at the new improvements to the Blazor component model, including required component parameters, generic type inference from ancestor components, JavaScript initializers, and handling of static web assets.

ASP.NET Core & Razor Pages are the foundations for many modern web apps. Check out what's new for ASP.NET Core MVC & Razor Pages in .NET 6 including Hot Reload, nullability checking, CSS isolation, Bootstrap 5, async streaming, IAsyncDisposable support, and faster build times.

Blazor in .NET 6 gives you the functionality you need to build real world apps of any size and complexity. In this session we'll look at the new Blazor features in .NET 6 for practical web app development. We'll look at the new support for Hot Reload, error boundaries, state preservation during prerendering, faster file uploads, query string handling, adding page metadata, and integrating Blazor components into existing JavaScript based apps.

Recap of keynote announcements and other great things in the conference!

Join Scott Hunter and team as they show you all the amazing things you can do with .NET 6.

Datadog is a monitoring and analytics platform for large-scale applications. It encompasses infrastructure monitoring, application performance monitoring, log management, and user-experience monitoring. Sreekanth Thirthala from Azure and Ryan MacLean from Datadog join Scott Hanselman to show how Datadog's offering in the Azure Marketplace enables you to manage Datadog in the Azure console as an integrated service.[0:00:00]– Introduction[0:00:51]– Overview of Datadog in Azure[0:04:08]– Demo of Datadog in Azure[0:10:22]– Datadog offering in Azure Marketplace[0:00:00]– Wrap-upNew Datadog integration with Azure offers a seamless configuration experienceWhat is Datadog?Datadog in Azure MarketplaceManage the Datadog resourceCreate a free account (Azure)

I've blogged before on how to easily move WSL distributions between Windows 10 machines with import and export. I recently did a full fresh install of Windows 11 and wanted to bring my existing highly customized Ubuntu installation along with me. You can tar up (zip up) the user-mode parts of your WSL2 distributions like this:wsl --export Ubuntu-20.04 c:TempUbuntuBackup.tarThe part after --export is the distribution name that you can see from running wsl --list -v. The last argument is a full path and filename for the archive you want created.Next, on the machine you've moved to, you'll do the reverse. Notice that I've changed the Distro name here, and you can if you want. Remember also that you can have as many Linux Distros installed as you want.wsl --import Ubuntu c:Linux c:TempUbuntuBackup.tarThe Linux file system is stored in a VHDX (virtual hard drive), usually deep in AppData/Local/YadaYada, but this import is an opportunity for me to store it in C:Linux which will also make it easier to do maintenance on like Compact-VHD which shrinks your WSL2 disks.Here's the weird part. When you import a WSL2 distro manually, running that distro on the new machine will end up logging you in as root. It's forgotten that I'm "scott."There's a lot of ways to fix this that involve the registry or passing in arguments to wsl, but I just want it to work when I run "wsl" or "wsl -d distroname."Run your distro, and then edit /etc/wsl.conf and add a [user] section like this:[user]default=scottThis is the ideal way to set your WSL distro's default user for imported tars because it's stored inside the Linux file system and the setting will stick around when you export/import later on. Hope this helps!Sponsor: Lob APIs ensure your addresses are deliverable and everything you send arrives at the right place. Add address autocompletion and verification in minutes using React, Vue or Javascript - Try for free!© 2021 Scott Hanselman. All rights reserved.     

I had a hard drive die recently so I decided to do a full fresh reinstall of Windows, this time a fresh Windows 11 from a downloaded ISO burned to a USB stick. It was a solid install and everything worked out of the box. I used it for a few days and had no issues, but while poking around I noticed in the Device Manager that there were dozens of Base System Devices that were banged out. Like a TON. I'd like to get that fixed, so I went to Windows Update but WU said everything was cool. Since a lot of stuff moved and was redesigned in Windows 11 I went looking for "Windows Update Optional Updates" and it took me a while to find it, even though it's listed right there on Windows Update in Settings. Click on Advanced Options. Here you can control things like your Windows Update active hours so it doesn't reboot when you don't want it, etc. Here you'll see a bunch of Optional Updates. I had like 33 of them. Here's what it looks like when you have a bunch of updates pending. These are Chipset and Motherboard updates. I did have to select each of these checkboxes and select Install at the end, but once they were done, I had no banged out (yellow exclamation point) devices in Device Manager. Hope this helps! Sponsor: Lob APIs ensure your addresses are deliverable and everything you send arrives at the right place. Add address autocompletion and verification in minutes using React, Vue or Javascript - Try for free!© 2021 Scott Hanselman. All rights reserved.