.NET

Yes, yes.

I used to use Windows machines and for historical reasons, yeah, any .NET developer used to have to use one.

But nowadays, even if you work in .NET with .NET Core and all of that, with a Mac OS or a Linux machine, you don't go through all of those troubles.

And I feel that most of these tools are built by teams using a MacBook, for example.

So they are...

Yeah.

So the blueprints initiate the process by having us navigate to google.com, search for .NET Core, and head straight to the official net.microsoft.com domain.

But, um, there's the detail here that immediately jumped out at me.

Oh, the 32-bit thing?

Yes.

The instructions explicitly specify downloading the 32-bit installer for .NET Core and running that executable.

I'll admit, that just stopped me in my tracks.

I mean, I completely get why.

Here's the first one.

April 2019, episode 24, talking with Iris Clason about migrating from ASP.NET to ASP.NET Core.

We'd gotten onto the subject of how much time developers spend keeping up to date.

And this is me.

one of the best developers she'd ever worked with, laid down out five.

Right, second one.

February 2022, episode 45, I'm talking to Nick Craver about migrating Stack Overflow to .NET Core.

I know a lot of .NET developers who are Windows and Microsoft Stack all the way, and there's nothing wrong with that.

I believe that it works outside of Visual Studio also, but I have not exercised that yet.

So once I migrate over to .NET Core, I'm going to find out because I'm using my Mac, which doesn't have Visual Studio.

So I'll be able...

I'll tell you if it does or not, but...

This is why you have to keep agreeing to cookies, as well as a bunch of other things like the right to be forgotten and serious fines for not being forthright with breaches.

Over on the Microsoft side of things in May, we have Build 2018, which ships .NET Core 2.1.

But also, and I realized this in hindsight when I was putting this together, is sort of the first wave of AI stuff.

Remember Visual Studio and Telecode? I think we did a show on it.

Yeah, it was TechEd.

That's where I'm at.

But yeah, but I'm also thinking about the craziness that was .NET Core in, you know, 2018 or 2016.

Because it took them 18 months to get that first version built, and there were so many previews.

It is powerful, mature, and deeply integrated into the Microsoft data ecosystem.

It is not a traditional NET reporting SDK.

The integration model is service-oriented.

You work with REST APIs, client-side embedding, authentication tokens, workspaces, and capacities.

There are documented rendering extensions and Office OpenXML support via additional packages.

Advanced, compliance-specific workflows are worth validating early on.

The documentation for ASP.NET Core covers multi-environment deployment and references Docker container considerations.

However, you will want to determine your exact container, font, and export requirements in a proof-of-concept.

Visual Studio 2017, which I don't think is a very remarkable version of Studio, except that it was really the version that started embracing the reality of we're in a GitHub Azure container world where we don't care what the operating system the container runs in.

We get .NET Core 1.1. They're putting together the tools for the way that we work today.

where you're deploying into the cloud using Linux-based containers.

So, you know, much more focused on Crossbot for 2017 was kind of the version there.