A few days ago, a number of .NET Core team members started reminding people that support for 1.x had ended. I took to dev.to and wrote an article reminding folks to upgrade. So I thought I’d start this newsletter with another subtle poke in that direction.
Seriously, go upgrade folks. You won’t get any support going forward if you don’t upgrade. And have a plan in place for upgrading all of your apps ahead of time, for the next time that a .NET Core version drops out of support.
With that out of the way, welcome to June’s first edition of The .NET Core Podcast newsletter. I hope that the summer is already treating you well
we recently had a heatwave in the UK and Europe, and it caught a lot of folks off guard - stay hydrated folks
For new subscribers, the format of the newsletter is usually:
One thing that I’m stoked about is that we’re a few weeks away from the one year anniversary of the first episode of the podcast. There were a few teaser episodes released ahead of it, but episode one was released on August 28th, 2018.
I have a few ideas for how we can celebrate one whole year of the podcast, but I’m keeping them close to my chest for the time being. Suffice to say, that being subscribed to the newsletter secures you one of the quickest ways to find out about the plans I have.
Also, did you know that the show recently blew past the 63,000 total downloads mark? But what does “total downloads” even mean? Well, here’s an explaation from the show’s podcast hosting provider:
> All time downloads tells you how many downloads the show has received all-time. This includes a combination of unique downloads and legacy downloads
So that’s 63,000 total downloads of the show since it’s creation. I have some great stats on the most popular shows, too. The stats allow me to infer some - probably entirely incorrect - ideas about which topics fans really want to hear. I’ll save them for a blog post on, or around, the anniversary date. So stay tuned.
Support for The .NET Core Podcast is provided, in part, by our Patreon supporters. To find out more about them, or to become a supporter of the show head over to our Supporters. Did you know that Patreon supporters get early access to full versions of each episode?
We also have a ko-fi page. This is for listeners who may not want to support us on a monthly basis, but more of an ad-hoc one.
And if that wasn’t enough ways to support the show, I’ve also created a “Buy Me a Coffee” page, which you can check out by clicking the following button:
But the best way that you can support the show would be to leave a rating or review in your podcatching service. Beit Apple Podcasts, Google Podcasts, Podchaser, Stitcher - wherever, really. That will help more folks find the show, which will mean that there’ll be more episodes.
This edition of the mailing list is sponsored by RJJ Software.
> Helping you to realise your company’s digital potential through innovative solutions using the latest technologies
Would you like to sponsor the show? Then check out our Sponsor page for details on what we have on offer.
This episode was published to Patreon supporters a few days ahead of the “regular” RSS feed on June 26, 2019 at 12:30 GMT.
This episode of The .NET Core podcast is a discussion on memstate and non-relational, no-SQL database technologies like memstate and how we can cut down on our database sizes without having to rely on those pesky mapping tables and foreign keys. You might be shocked to hear just how much data Robert claims to be able to hold in the RAM of a “modest desktop”
It was later released to the “regular” RSS feed on June 28, 2019 at 12:30 GMT. The show notes, including a transacription, are available at: Episode 28 - memstate with Robert Frieberg.
This episode will be published to Patreon supporters a few days ahead of the “regular” RSS feed on July 10th, 2019.
This episode is the first one with more than just one guest, and I couldn’t have asked for better people for my first three person episode. Jasmine Greenway and Cecil L Philips are both Developer Advocates at Microsoft, and work on getting out feedback directly to the development teams at Microsoft. But they both do so much more than that. You’ll have to listen to the episode when it comes out, to learn just how much they both do on a daily basis.
On release day, you’ll be able to check out the show notes at: Episode 29 - Education and Development with Jasmine Greenaway and Cecil L Philip
This episode was the first interview episode_I assume that you already do, becauseRecebat I had for the podcast.
Inside baseball fans might be interested to know that I’d already written and recorded the monologues for .NET Standard (episode 4), Mono (episode 6) and ASP.NET Core (episode 8) before interviewing Dustin.
This was a great conversation with Dustin about CoreWF, Windows Workflow, and some interesting tidbits about how .NET Framework works - including a little insight into the makeup of the repos for .NET Framework.
Full show notes, including a full transcript of the episode and an embedded player are available here
I don’t currently have any speaking engagements lined up, but I’m looking at a number of (UK based) conferences and meetups that I’d like to attend. I’ll keep this portion of the newsletter updated (in later editions) with the list of places events that I’ll be attending, and if you’re around then find me and say hi. I like to think that I’m an approachable sort of chap - and I might have some swag to give away.
If you’re at all interested in having me speak at your event, then please get in touch. The best way is to follow me on Twitter and send me a DM (they’re always open).
You can subscribe to the show in a number of ways, here are links to a number of podcasting services which have the show listed:
One of the most important pages relating to .NET Core
or as it’ll soon be known “.NET 5” - more on that in a future episode of the show
The support page lets you know when each version of .NET Core will be going out of support. The most interesting part of the page is the .NET Core Release Lifecycles table:
|Version||Original Release Date||Latest Patch Version||Patch Release Date||Support Level||End of Support|
|.NET Core 3.1||Scheduled for November 2019||Will be LTS when released|
|.NET Core 3.0||Scheduled for September 23, 2019||Will be Current when released|
|.NET Core 2.2||December 4, 2018||2.2.5||May 14, 2019||Current||December 23, 2019|
|.NET Core 2.1||May 30, 2018||2.1.11||May 14, 2019||LTS||At least three years from LTS declaration (August 21, 2018)|
|.NET Core 2.0||August 14, 2017||2.0.9||July 10, 2018||EOL||October 1, 2018|
|.NET Core 1.1||November 16, 2016||1.1.13||May 14, 2019||Maintenance||June 27 2019|
|.NET Core 1.0||June 27, 2016||1.0.16||May 14, 2019||Maintenance||June 27 2019|
(the above table is correct at the time of creating this edition of the newsletter - please see this link for the very latest version of it1)
What’s interesting is the fact that version 2.2 goes out of support before version 2.1. There’s a very simple reason for this, as was discussed on several ASP.NET Community Standups recently.
disclaimer: I do not work for Microsoft, and the following is based on blog posts and episodes of the ASP.NET Community Standup
as ASP.NET Core 2.1 on .NET Framework 4.6+ is going to be supported for a little longer, in order to allow folks time to transition over from Framework to Core. But even that support will end in 2021, at which point .NET Core 3.0 will be the LTS before .NET 5 gets that level of support.
Who doesn’t love a good look ahead at what’s coming?
For the folks who haven’t had a chance to play with the previews of .NET Core 3.0, this slide deck will give you enough teasers to make you want to go out and install the latest preview on a dev machine and try them all out.
My favourite thing so far is something the dev team are calling “ReadyToRun” which is a publishing target. Essentially, this will provide an AOT (Ahead of Time) NATIVE BUILD of your app. The compiled binaries will be slightly larger than a standard publish, but they promise much faster startup times.
psst. remember this command
dotnet publish /p:PublishReadyToRun=true
The authors of my favourite IDE
I don’t class VS Code as a full IDE because you need to install plugins for everything; but it’s a VERY good C# editor and debugger
have implemented a WinForms editor ahead of the full release of .NET Core 3.0. And this is because 3.0 is bringing support for WinForms and WPF - to Windows only, though.
I’ve been wanting to use Rider and .NET Core 3.0 to work on some of my older WinForms apps (including both WDTV-Live-Meta-Gen and RockPaperScissors) and am really looking forward to giving this a try.
Here are some awesome Communities Where you can find me:
yet another podcast-based Slack that you can join, but this time run by me. plus, Patrons get their own area separate from everyone else where they can suggest topics. I’m also doing an AMA with them via this, too