The .NET Stacks #1: Microsoft Build, announcements galore!

We discuss all of the Microsoft Build news!

Dave Brock
Dave Brock

This is an archive of my weekly (free!) newsletter, The .NET Stacks. Consider subscribing today to get this content right away! Subscribers don’t have to wait a week to receive the content.

Welcome to the very first issue of The .NET Stacks! I appreciate all of you for being my first subscribers—even before it was even launched. If you have any suggestions, you can simply reply to this email or hit me up on Twitter. And if you like what you see, I would love for you to share with others as well. Let’s get started!

3 things to keep you informed

The three things you need to know to keep you current and impress your colleagues (the details of which are in this newsletter):

  1. Blazor Web Assembly support is now live! This gives you the ability to debug C# in the browser and use one language for your entire development experience (while you may need to use some interop libraries). Need to work on the front-end, but don’t have a team with a good JavaScript skillset? Are you a one-person shop too overwhelmed to learn JavaScript? Well, there you go.
  2. With .NET 5, to be released in November 2020, comes the vision of “One .NET,” including Xamarin! A core tenet is producing one .NET runtime and framework that can be used everywhere.
  3. C# 9 is coming along, which brings a ton of improvements like init-only properties and records (among many, many other things)

Microsoft Build

As you may have heard, Microsoft Build occurred this week—from the comfort of our homes. The real question is: will we ever want to go back, after having this go so seamlessly?

All the content is available for on-demand viewing on the Build site and Channel 9. Here are the keynotes:

On top of the keynotes, there were several valuable break-out sessions that you can watch at your convenience. Of course, a ton of announcements/news:

Thought of the week

For many of us who have been writing .NET for awhile, we can easily split Microsoft into two companies: the Gates/Ballmer years (“OId Microsoft”), with its resistance to open source in favor of world dominance and Microsoft lock-in; and two, the kindler/gentler Microsoft who strives to be open to all, in favor of driving business to its Azure offerings (“New Microsoft”).

When New Microsoft announced the Windows Package Manager, it was met with quite a bit of skepticism from the community, and caused one spirited GitHub discussion. Leaders in the space, like Chocolatey, don’t seem to be worried yet, but some folks in the community are asking: why is this needed, with so many community projects out there that already solve this problem (or are further along)? Microsoft points at the issues delivering a native app as well as security considerations.

Microsoft’s stance of “if you are happy with what you use, great” comes off to some as a little naive, considering how the remnants of Old Microsoft still linger to some folks. As for the community, some patience would help without jumping to conclusions, as Microsoft has open-sourced this and is open to feedback—and New Microsoft has a track record of working with developers, not against them.

From the community

This section is a bit brief because of all the Build announcements, but alas:

What are you building?

Care to show off what you’re building? Reach out at, and it might be featured in a future newsletter.

Tweet of the week

tweet of the week


I would love to hear any feedback you have for The .NET Stacks! For a little while, I’ll be trying some new things—as with software, some might work and some might not. My goal is to make this the one-stop shop for weekly updates on developing in the .NET ecosystem, so I look forward to any feedback you can provide. You can directly reply to this email, or talk to me on Twitter as well. I’ll talk to you next week!

.NET Stacks