.NET 6 was released last week; .NET 5 has 6 more months of support, and Chrome decides “view source” is bad.
🚄Announcing .NET 6 — The Fastest .NET yet new features include Minimap APIs, Hot Reload for Visual Studio and the .NET CLI, C# 10, better performance, a “Unified platform” for development, and lots, lots more.
🧥Announcing ASP.NET Core in .NET 6 Hot Reload makes an appearance, of course, as done Minimal APIs, and lots of improvements for Blazor, and as I said at the top, lots more.
🎂Cake v2.0.0 RC 1 released Lots of bug fixes in this one, and the cake is not a lie.
🏃♀️.NET Everywhere – Windows, Linux, and Beyond Scott Hanselman demos .NET across platforms, as the title indicates. It’s super weird for Microsoft to have a “Windows Visual Studio only” mentality on one hand and a “but you can run .NET anywhere” mentality on the other.
🚫🛠Chrome allows admins to disable “View Source” and this has started a bit of a brouhaha. On one hand, people on the internet are mad that this feature exists, on the other hand people on the internet say it’s no big deal. It’s both. You don’t improve internet literacy by giving in to companies that put the answers to their exams in the HTML, and you certainly don’t lend credence to the idea that View Source is some sort of crime.
🎸EF Core 6.0 hops on the minimal API bandwagon. Don’t worry, the kitchen sink is still there.
🕸Orleans supports .NET 6 with release 3.5.1 Orleases is Microsoft’s approach to ‘distributed .NET’ on public cloud servers. It’s fascinating (and used by Microsoft) and it now supports .NET 6. No word yet on who outside of Microsoft needs this, however.
⌚EF Core 6.0 has been released. It includes temporal tables, pre-convention configured models, and more.
🧯The Hot Reload docs are live. Microsoft is a bit late to this party, so maybe that’s why they’re all in on the docs? In other stacks, it’s just the way.
🔮Powershell 7.2 has been released and it includes bug fixes plus predictive intellisense (if you use PSReadLine), which seems pretty neat.
🎭Nuget 6.0 has been released Includes Sourcemapping, Package Vulnarabilities…. wait. Package Vulnerabilities? Oh, it can show you package vulnarabilies in Visual Studio. NuGet is a major part of .NET and is still pretty tightly coupled to Visual Studio. Until Microsoft fixes that issue, I don’t see the claims of ‘.NET everywhere’ coming to fruition. If you want a first-class experience with Nuget, you’re still limited to Visual Studio.
🙊The EF Core team fixed 545 issues for EF Core 6.0. The EF Core team is 5 engineers, 1 manager, and a PM. Let’s say they started on work for .NET 6 / EF Core 6.0 On January 15th, 2021 (.NET 5 was released in november of last year; but you can imagine they had to work on patches for that, and hopefully took some time off for the holidays). .NET 6 was released on November 8th, 2021. That means there are 203 work days (excluding weekends and holidays). With 545 issues fixed, and 5 working members of the team, that’s an issue resolved every 2 days per person. That is a frantic pace; and given what we saw for .NET 5; that means the EF Core team has not had a break in over 2 years from a frantic pace. Their manager explains this as “passion”:
Or we’re just that good. 🤣😉 (Joke)
Five engineers, a manager, and a PM. And we mostly just chug along. We don’t do heroics. What fits, fits. What doesn’t gets punted. That being said, there’s a lot of passion on the team, and it’s more than just a job for some of us at least. (emphasis mine)
I have to say I’m a bit concerned about the work/life balance for the EF team, and it raises a whole lot of red flags to see this sort of pace for the last 18 months.
🐦Jeremy Sinclair livetweets the .NET 6 release .NET 6. Now .NET 6 is the LTS version of .NET that finally sheds the Framework mantle (.NET 5 wasn’t LTS), and so you should see .NET 6 as the first major .NET Version that legacy companies migrate to.
⁉Steve shows off implicit global usings One of the major problems I’ve had with code samples on the internet is the namespaces not being included in the code sample. This makes that worse, and easier to happen. I like the idea, but the implementation doesn’t help our current set of problems with getting code off the internet.
🚢NativeAOT coming in .NET 7 This will allow for a statically linked ‘single file’ deployment to all platforms, a la Go.
🧥Full-stack .NET 6 Apps with Blazor WebAssembly and Azure Static Web Apps Since Blazor can support WebAssembly, and Static web apps are just that; you can now deploy Blazor apps to Azure Static Web Apps. I’m interested to see what sort of frameworks around Blazor pop up.
💸CSharpFritz (Jeff Fritz) plays Pitchman for Mobile.NET’s product that convert’s Webforms to “Native Web App”. This is interesting inasfar as Jeff works for Microsoft on the .NET team, and Mobilize.NET (as far as I know) is a third-party vendor — why is Microsoft pitching other companies’ products?
📹Visual Studio 2022 has been released and Scott Hanselmen (and friends) take you through what’s new. There’s also a blog post if you aren’t the ‘watching videos on the internet’ type.
It was a busy week last week with the release of .NET 6; and hopefully the folks at Microsoft are going to take a bit of extra time off for Thanksgiving. See you all next week.