• Performance improvements in the core debugger
• Support for  .NET 6 , which can be used to build web, client and mobile apps by both Windows and Mac developers, as well as improved support for developing Azure apps
• An update UI meant to reduce complexity and which will add integration with Accessibility Insights. Microsoft plans to update the icons and add support for  Cascadia Code , a new fixed-width font for better readability
• Support for C++ 20 tooling. language standardization and Intellisense
• Integration of text chat into the  Live Share  collaboration feature
• Additional support for Git and GitHub
• Improved code search  

Bringing WebAssembly to the .NET Mainstream - Steve Sanderson, Microsoft

Many developers still consider WebAssembly to be a leading-edge, niche technology tied to low-level systems programming languages. However, C# and .NET (open-source, cross-platform technologies used by nearly one-third of all professional developers [1]) have run on WebAssembly since 2017. Blazor WebAssembly brought .NET into the browser on open standards, and is now one of the fastest-growing parts of .NET across enterprises, startups, and hobbyists. Next, with WASI we could let you run .NET in even more places, introducing cloud-native tools and techniques to a wider segment of the global developer community. This is a technical talk showing how we bring .NET to WebAssembly. Steve will demonstrate how it runs both interpreted and AOT-compiled, how an IDE debugger can attach, performance tradeoffs, and how a move from Emscripten to WASI SDK lets it run in Wasmtime/Wasmer or higher-level runtimes like wasmCloud. Secondly, you'll hear lessons learned from Blazor as an open-source project - challenges and misconceptions faced bringing WebAssembly beyond early adopters. [1] StackOverflow survey 2021 

• Overhauled memory management for vacuuming, resulting in significantly lower memory usage and running time. More on this here.
• Incremental backup support.
• Faster B-tree index scans.
• MERGE enhancements, including view support.
• New functions to extract elements from UUIDs.
• WAL improvements – up to 2x write throughput on some workloads.
• Improvements to SQL/JSON support, including JSON_TABLE.
• Bulk loading improvements and perf improvements for COPY which gains the ON_ERROR ignore option to ignore errors.
• Identity columns on partitioned tables.

You do not need to register, or anything, just visit the course and all the videos are available as ‘previews’. You will be able to take the entire course without even giving me any personal information! The courses include:

Bootstrap 4

Using Vue with ASP.NET Core By Example

SignalR in ASP.NET Core Projects by Example

Integrating SignalR and Vue

Integrating SignalR and Angular

I always love talking to Julie! She first spends some time discussing some of the new things in Entity Framework 7 and when one should consider using (and more importantly not using) the new bits. She also gets into her experience working with Aurelia and node.js. Enjoy! 

Retirement of MCSA, MCSD, MCSE certifications and related exams extended

We know many of you are working toward completing your Microsoft Certified Solutions Associate (MCSA), Microsoft Certified Solutions Developer (MCSD), or Microsoft Certified Solutions Expert (MCSE) certification(s). We realize that the current environment could potentially hamper your ability to finish your certification before the original retirement date of June 30, 2020. To address this issue, we are extending the retirement date for these specific certifications to January 31, 2021 to give you more time to complete the exams and earn your certification. 

This is something that I'm pretty familiar with as I was a self-taught software developer myself.

And in this video, I'm going to tell you why it's better to become self-taught rather than going to college for software development, and how you can do this. 

The CLI offers a new generator to easily create interceptors! 

DARPA Wants All C Converted To Rust

After more than two decades of grappling with memory safety issues in C and C++, the software engineering community has reached a consensus. It’s not enough to rely on bug-finding tools. The preferred approach is to use “safe” programming languages that can reject unsafe programs at compile time, thereby preventing the emergence of memory safety issues.

I haven’t really been hiding this, but I apparently need to be more clear that I do not intend to do any further development work on StructureMap other than trying to keep up with pull requests and bugs that have no workaround.