TRASCRIZIONE 🔗
WEBVTT
00:00:00.239 --> 00:00:03.600
.NET 8 and.NET 9 both expire in November.
00:00:03.759 --> 00:00:15.519
I've seen some questions about this, including if long-term support or LTS is still a thing, and why.NET 9 is already expiring when.NET 10 has only been out for a year.
00:00:15.839 --> 00:00:20.079
The reality is that.NET 9 support was actually extended.
00:00:20.239 --> 00:00:30.800
But let's talk about what LTS versus STS means, why this process is so fast, and what will be supported going forward in today's episode of Dev Questions.
00:00:39.039 --> 00:00:42.560
Welcome to the DevQuesti podcast with Tim Corey.
00:00:43.119 --> 00:00:45.679
Software development is more than just writing code.
00:00:45.840 --> 00:00:47.280
So let's talk about the rest of it.
00:00:47.439 --> 00:00:55.600
Specifically, let's talk about the changes to STS and why we have two versions of.NET going out of support at the same time.
00:00:56.000 --> 00:01:00.960
Now, let's start with what is LTS and what is STS?
00:01:01.039 --> 00:01:06.159
We've talked before about this, but LTS is the long-term support for.NET.
00:01:06.319 --> 00:01:11.840
So when an LTS version comes out, and they're the even versions, so 8, 10, 12.
00:01:12.159 --> 00:01:26.640
So when.NET 10 came out, it was supported, or will be supported for three years, which means that when it came out last year in 2025, it'll be supported through 2028 at the same time.
00:01:26.719 --> 00:01:30.799
So November is when it came out, it will be supported through November of 2028.
00:01:31.040 --> 00:01:35.760
An STS version used to be supported for 18 months.
00:01:35.840 --> 00:01:37.599
So it'd come out in November.
00:01:37.840 --> 00:01:44.000
And let's say.NET 9 came out in, was it 2024?
00:01:44.159 --> 00:01:48.799
So it was supported through 2026 in May.
00:01:49.040 --> 00:01:50.799
Well, they said, hey, you know what?
00:01:50.959 --> 00:01:56.560
Instead of extending it to May, let's extend it even further and make it supported for two years.
00:01:56.719 --> 00:01:58.640
So instead of 18 months, two years.
00:01:58.799 --> 00:02:05.120
So it's supported then through the the same time as the LTS version.
00:02:05.280 --> 00:02:10.000
That way there is no penalty for going to an STS version.
00:02:10.319 --> 00:02:23.759
So if you're on.NET 8 and you said, hey, let's go upgrade a.NET 9, well,.NET 9 went out of support before.NET 8 did, which kind of gives you a penalty for going to the STS version.
00:02:24.000 --> 00:02:28.080
So Microsoft changed that so that it's three years and two years.
00:02:28.319 --> 00:02:36.560
That way the 9 and 8 expiration date, which is November of this year, goes out of expiration at the same time.
00:02:36.960 --> 00:02:46.000
Their NS support is the same time, which means that you can go from.NET 8 to.NET 9 and not have any penalty for doing so.
00:02:46.240 --> 00:02:48.560
You still have to upgrade on a schedule.
00:02:48.639 --> 00:02:57.360
You still have to make sure that you're moving forward, but it's not something you have to then think, oh, we have to go even faster a.NET 10.
00:02:57.520 --> 00:02:58.080
You don't.
00:02:58.240 --> 00:03:01.280
You now have two years instead of 18 months.
00:03:01.520 --> 00:03:09.120
Now the way this, the reason this way works this way is because Microsoft can't support everything forever, right?
00:03:09.360 --> 00:03:20.560
There's um new security updates that have to happen all the time and trying to backport those into different versions really takes a lot of time and effort and it's very costly.
00:03:20.800 --> 00:03:26.240
So the other thing is that we used to have a longer LTS version.
00:03:26.400 --> 00:03:29.759
With.NET framework the LTS lasted a lot longer.
00:03:29.919 --> 00:03:33.280
But that's because we got updates a lot less.
00:03:33.520 --> 00:03:39.520
So what was happening was we'd get you know three, four, five years between an update.
00:03:39.680 --> 00:03:45.599
And so yeah, they were supported for longer because there was no new version to go to beyond that one.
00:03:46.879 --> 00:03:51.360
The problem with that is that your code starts to rot a bit.
00:03:51.599 --> 00:03:59.599
And what I mean by that is you start to settle where your your dependencies may start to change but you're like ah I'm not going to upgrade those.
00:03:59.680 --> 00:04:02.319
I don't want to you know touch anything it's it's working.
00:04:02.639 --> 00:04:17.920
And all of a sudden a new version of.NET comes out but it because it was so long coming out there's a lot of changes and potentially a lot of breaking changes in how it works, which means a very high bar to get to the next version.
00:04:18.160 --> 00:04:22.000
And so companies would kind of go, we just can't do it.
00:04:22.319 --> 00:04:26.480
It's just too much work to get from one to the next and so we're going to stay here.
00:04:26.639 --> 00:04:36.480
And that's why you still see companies today that are on.NET framework or.NET framework 3.5 even not even 4.8 the latest.
00:04:36.720 --> 00:04:43.439
So they're kind of stuck in older version or a very older version and they feel like they can't move forward.
00:04:43.759 --> 00:04:53.279
Microsoft's philosophy was hey let's help these companies move forward by making that step-by-step progression much, much easier.
00:04:53.519 --> 00:04:58.319
I have a number of.NET apps that came out in previous versions of.NET.
00:04:58.480 --> 00:05:03.680
I have one app that was.NET 6 originally I believe it's a suggestion site app was.NET 6.
00:05:03.839 --> 00:05:06.959
I've upgraded that all the way to 10 just by changing the numbers.
00:05:07.279 --> 00:05:16.959
So it gets the benefits of the upgrades and there are significant benefits to just changing the number but it's also a very easy process.
00:05:17.120 --> 00:05:23.439
Now I'm not saying that your production app is just going to be changing a number because you have dependencies.
Load full transcript
00:05:23.519 --> 00:05:35.920
And those dependencies, yeah, they're going to need to make sure that you make changes there because some dependencies go out of support as well and maybe you can't just upgrade those and so you're kind of stuck there.
00:05:36.079 --> 00:05:53.759
The other thing is if you're using deprecated things, which there aren't many in.NET.NET really tries hard not to deprecate things and not to stop supporting those things going forward or at least have those things you know still in the in the language in the framework.
00:05:54.319 --> 00:06:00.560
So there's not many things that that are breaking changes that are are massive issues, but there are some.
00:06:00.800 --> 00:06:04.959
And so if you have one of those, yeah, that's going to take more work as well.
00:06:05.120 --> 00:06:11.759
So it's I'm not saying it's just a number change like it is for me because I have less dependencies in a smaller app.
00:06:12.079 --> 00:06:17.120
But it's a very easy change compared to a.NET framework upgrade.
00:06:17.439 --> 00:06:42.079
So this allows Microsoft to move faster, which allows us to get better things quicker into our applications and it allows our applications to be upgraded more frequently and more easily so that we can potentially stay on the latest versions, which make sure we it protects us against things like new security issues.
00:06:42.399 --> 00:06:53.600
So with all of that we have.NET 8 and.NET 9 for the first time we have two versions of.NET expiring at the same time in November.
00:06:53.839 --> 00:06:54.240
Why?
00:06:54.399 --> 00:06:56.000
Well we already have.NET 10.
00:06:56.079 --> 00:06:59.120
We've had.NET 10 for almost a year now.
00:06:59.279 --> 00:07:06.240
So this is being recorded in October so we have one more month of.NET 10 before it's been out for a year.
00:07:06.399 --> 00:07:08.240
But then we get.NET 11.
00:07:08.399 --> 00:07:13.279
So we'll have.NET 10 which is the LTS version, a long-term support version, three years.
00:07:13.519 --> 00:07:15.519
We have that it's been out for a year.
00:07:15.680 --> 00:07:22.959
And we have.NET 11 now, which is the STS version, which will be supported for two years.
00:07:23.279 --> 00:07:30.879
So that means that we now have two versions of.NET when the other two go out of support.
00:07:31.199 --> 00:07:34.959
Now let's talk really briefly about what does out support mean?
00:07:35.120 --> 00:07:40.959
Because some people think that means that there's a big switch somewhere at Microsoft, they pull that switch and the lights turn off.
00:07:41.120 --> 00:07:42.800
And that's not really what happens.
00:07:43.040 --> 00:07:50.480
What end of support means is that there's not going to be more patches for that.NET version.
00:07:50.639 --> 00:07:56.720
So if there's a security flaw or something else that comes out that will not be fixed in the older versions.
00:07:57.040 --> 00:08:06.959
So that's the support you would get normally with your.NET
language which means your.NET language 8, 765, these still work.
00:08:07.279 --> 00:08:12.879
It's just they're not supported with new security fixes or bug fixes or other things.
00:08:13.199 --> 00:08:18.399
So if it's still working it's not going to turn off because November hits.
00:08:18.639 --> 00:08:27.360
However for security reasons you really want to be on a supported version of.NET Okay?
00:08:27.920 --> 00:08:44.080
So that's why when I recommend people you know with to use.NET I say hey I want you to stay on the latest version of.NET and I actually encourage companies to use the STS version as well not just the LTS version.
00:08:44.159 --> 00:08:49.759
And here's why because when you move from one version to the next it's a small step.
00:08:49.919 --> 00:08:51.759
There are very few breaking changes.
00:08:51.840 --> 00:08:58.559
There are very few things that have to change in your application and hopefully your dependencies stay up to date.
00:08:58.799 --> 00:09:12.159
The other thing is that by doing that small step twice, it's much easier to do than having one step that you do that's a little bit larger from say eight to 10, especially if you go like six to 10.
00:09:12.240 --> 00:09:22.879
There's lots of changes that have happened but if you did it a bite at a time as opposed to trying to eat the whole elephant at once then you you got a much easier process.
00:09:23.360 --> 00:09:27.919
So I recommend people going on every single version of.NET.
00:09:28.240 --> 00:09:34.159
And yes, that means that every year you're doing some work on your application to upgrade it.
00:09:34.320 --> 00:09:42.559
However, I recommend that every time you do an upgrade that you work on automating the process work on streamlining the process.
00:09:42.720 --> 00:09:48.879
If you have a dependency that causes a problem every time evaluate that dependency if it's really worth it.
00:09:49.120 --> 00:09:53.519
Maybe you can get around that dependency by not having it.
00:09:53.919 --> 00:09:58.000
Oftentimes companies will take dependencies that they don't actually need.
00:09:58.159 --> 00:10:04.559
Maybe they use 5% of a dependency but it was easy just to put it in well take it out.
00:10:04.799 --> 00:10:10.320
Do it yourself or use a different dependency that's more reliable or more easily updated.
00:10:10.639 --> 00:10:18.960
So make that process easier and easier so you can get faster and faster at it, which means that you're continually trimming and cleaning your code base.
00:10:19.120 --> 00:10:30.480
You're continually making your code base better, which also means that when you get the new version you make your code base faster because every version of.NET includes performance improvements.
00:10:30.960 --> 00:10:33.440
And that's really your your carrot, right?
00:10:33.600 --> 00:10:41.519
When you're talking to management and saying hey I want to upgrade our version of.NET and they see no reason to do so, talk about the security issues.
00:10:41.679 --> 00:10:54.000
Talk about the fact that you want to stay on a version that is supported because of those security issues but then also talk about that carrot which is we'll also get performance improvements out of this.
00:10:54.320 --> 00:10:59.759
So if you find yourself falling behind now is a great time to start working on an upgrade plan.
00:11:00.000 --> 00:11:15.200
Because with.NET 11 coming out and.NET 8 and 9 going out of support in a month, it's a great time to start planning to start working towards changing how you do things and start working towards that upgrade process.
00:11:15.360 --> 00:11:20.240
And you can upgrade a.NET 10 right now because you'll have two more years of support.
00:11:20.399 --> 00:11:30.720
But then when 11 comes out you just did 10, you know what the process looks like it might be a good thing to go to 11 as well just to keep that momentum going.
00:11:30.879 --> 00:11:31.200
Okay.
00:11:31.759 --> 00:12:00.000
So part of this plan is going to be communicating and making sure that you communicate the importance of the upgrades use that carrot of we're going to improve speed while at the same time use the kind of the hammer of hey we need to make sure that we're protecting our application because our our company depends on this application and we can't have security issues that we have to fix right away or they endanger our company or our customers.
00:12:00.240 --> 00:12:10.399
So we want to stay on a supported version okay work with management make sure they understand the both the importance of the upgrades but also the benefits as well.
00:12:10.639 --> 00:12:13.919
Thanks for listening and as always I am Tim Corey.
00:12:14.399 --> 00:12:17.360
Thank you for joining us for this episode of Dev Questions.
00:12:17.519 --> 00:12:25.840
When you're ready to learn to think and code like a professional developer head over to I amtimcorey.com and enroll in a course