Outdated?
-
So, I fire up VS2019 today to write a small console app; then you choose a framework, and all my choices have this nice prefix "no longer supported". There's that new-fangled .NET Core 3, and it is already no longer supported. You mean 5 years is too long to support your product? Why would I even look at the new products then, as they are already on their way to being unsupported?
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
So, I fire up VS2019 today to write a small console app; then you choose a framework, and all my choices have this nice prefix "no longer supported". There's that new-fangled .NET Core 3, and it is already no longer supported. You mean 5 years is too long to support your product? Why would I even look at the new products then, as they are already on their way to being unsupported?
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Apparently. .NET and .NET Core official support policy[^] Though it is rather difficult to release new versions and support old versions at the same time. If one supposes 10 years then they would need to support 10 different versions (from that list.) This becomes more problematic if one of those versions has a security problem and fixing it would require significant work and/or a refactor.
-
Apparently. .NET and .NET Core official support policy[^] Though it is rather difficult to release new versions and support old versions at the same time. If one supposes 10 years then they would need to support 10 different versions (from that list.) This becomes more problematic if one of those versions has a security problem and fixing it would require significant work and/or a refactor.
I rarely code at all any more and never using MS stuff, so please help me understand that chart from your link. Using the .NET Core 3 that Eddy mentioned... Original Release Date: September 23, 2019 Last patch version (v3.0.3): February 18, 2020 (148 days since original release) End of support: March 3, 2020 (162 days since original release) 162 days!?!?!?!?!? What am I missing?
-
Apparently. .NET and .NET Core official support policy[^] Though it is rather difficult to release new versions and support old versions at the same time. If one supposes 10 years then they would need to support 10 different versions (from that list.) This becomes more problematic if one of those versions has a security problem and fixing it would require significant work and/or a refactor.
You know why JavaScript has that many equality operaters? Because it would break a lot of existing code if they simply changed it and called it outdated; a big part of the internet would break down. I dislike JavaScript, but it is reliable. Do new idea's have to break the principle of reliability? No, they don't. Unreliable means exactly that.
jschell wrote:
This becomes more problematic if one of those versions has a security problem and fixing it would require significant work and/or a refactor.
Maybe stop introducing new crap every three months that introduces more bugs and security riscs? :)
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
I rarely code at all any more and never using MS stuff, so please help me understand that chart from your link. Using the .NET Core 3 that Eddy mentioned... Original Release Date: September 23, 2019 Last patch version (v3.0.3): February 18, 2020 (148 days since original release) End of support: March 3, 2020 (162 days since original release) 162 days!?!?!?!?!? What am I missing?
fgs1963 wrote:
What am I missing?
I blame marketing. Ever since Windows was invented, buttons had to look "newer" with every version. Change, for changes sake, to prove things "improved".
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
I rarely code at all any more and never using MS stuff, so please help me understand that chart from your link. Using the .NET Core 3 that Eddy mentioned... Original Release Date: September 23, 2019 Last patch version (v3.0.3): February 18, 2020 (148 days since original release) End of support: March 3, 2020 (162 days since original release) 162 days!?!?!?!?!? What am I missing?
fgs1963 wrote:
What am I missing?
3.1 has just over two years support. I think they didn't formalise the STS/LTS cycle until .NET 5, which was the first version to have precisely 18 months support.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
fgs1963 wrote:
What am I missing?
3.1 has just over two years support. I think they didn't formalise the STS/LTS cycle until .NET 5, which was the first version to have precisely 18 months support.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
A good thing they don't build pacemakers.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Or bionic implants: Bionic Implants Can Go Obsolete And Unsupported, Too | Hackaday[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
So, I fire up VS2019 today to write a small console app; then you choose a framework, and all my choices have this nice prefix "no longer supported". There's that new-fangled .NET Core 3, and it is already no longer supported. You mean 5 years is too long to support your product? Why would I even look at the new products then, as they are already on their way to being unsupported?
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
I blame Linux for that. 5 years is considered "LTS" (Long-Term Support). Somehow Microsoft thought that was a great idea and adopted that schedule. Phones are even worse.
-
Or bionic implants: Bionic Implants Can Go Obsolete And Unsupported, Too | Hackaday[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
So, I fire up VS2019 today to write a small console app; then you choose a framework, and all my choices have this nice prefix "no longer supported". There's that new-fangled .NET Core 3, and it is already no longer supported. You mean 5 years is too long to support your product? Why would I even look at the new products then, as they are already on their way to being unsupported?
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Why are you not using 2022? It's not like .net changes wildly. I've just done projects to uplift to . net 6 and it's never true I need to change code.
-
So, I fire up VS2019 today to write a small console app; then you choose a framework, and all my choices have this nice prefix "no longer supported". There's that new-fangled .NET Core 3, and it is already no longer supported. You mean 5 years is too long to support your product? Why would I even look at the new products then, as they are already on their way to being unsupported?
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
I really don't know "what I'm on" other than VS2022. I just keep adding projects to a solution I created about 4 years ago. Console is "console". UI is UWP. Class libraries are Standard 2.0 so I can use them in both. All I know is it works and it lets me do what I want.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
Phones aren't required.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Have I just met the second (of three people) on this planet who agrees with me and doesn't carry around a phone? :~
-
Why are you not using 2022? It's not like .net changes wildly. I've just done projects to uplift to . net 6 and it's never true I need to change code.
Christian Graus wrote:
Why are you not using 2022?
What year is this? Because I do not need to. I prefer flipping burgers.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
I really don't know "what I'm on" other than VS2022. I just keep adding projects to a solution I created about 4 years ago. Console is "console". UI is UWP. Class libraries are Standard 2.0 so I can use them in both. All I know is it works and it lets me do what I want.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
I do not care about what an UWP is.
Gerry Schmitz wrote:
All I know is it works and it lets me do what I want.
You're a developer. I'm a programmer.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
So, I fire up VS2019 today to write a small console app; then you choose a framework, and all my choices have this nice prefix "no longer supported". There's that new-fangled .NET Core 3, and it is already no longer supported. You mean 5 years is too long to support your product? Why would I even look at the new products then, as they are already on their way to being unsupported?
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Out of curiosity, I fired up VS2019 and (when it eventually gave me a UI) clicked "new project". I'm still looking at three empty drop-down boxes and two spinning wheels. [Update- the wheels are no longer spinning, just frozen]. [update 2 - I now have the option of 4 .Net Framework projects (class library, winforms, wpf forms, wpf user control, wpf custom control), a .Net Standard class library, or a .Net Core class library. Glad I normally just stick with VS2015 and don't allow it to update... :laugh: [Update 3 - much, much later, having selected .Net Core class library, I get a code editor window. An error message at the top tells me "There was an error activating the remote language server, C#/VB Language Server Client"... WTF is that? There's a link for more info, and it opens an XML log file in... Internet Explorer. (I didn't know this machine still had a copy of IE on it!!!)
Telegraph marker posts ... nothing to do with IT Phasmid email discussion group ... also nothing to do with IT Beekeeping and honey site ... still nothing to do with IT
-
My phone stays home. I aint important enough to be always available.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Eddy Vluggen wrote:
I aint important enough to be always available.
That's exactly what I keep telling others. I don't get why people need to call each other to say "I just left work, I'll be home in 20 minutes". Before the smartphone, nobody picked up their office phone to call home to say they were on their way. When I was a kid, I've never seen my mother call my dad at work (or vice-versa) unless, I dunno...someone died? And even then, it would've had to be someone close. Then they their brain tries to label me as some sort of luddite, which really confuses them since, in my circle of friends/family, as I'm the go-to guy for technical problems. They assume I live on Facebook. I've never even had an account on Facebook, and honestly believe we'd all be better off if the whole site was shut down.
-
Eddy Vluggen wrote:
I aint important enough to be always available.
That's exactly what I keep telling others. I don't get why people need to call each other to say "I just left work, I'll be home in 20 minutes". Before the smartphone, nobody picked up their office phone to call home to say they were on their way. When I was a kid, I've never seen my mother call my dad at work (or vice-versa) unless, I dunno...someone died? And even then, it would've had to be someone close. Then they their brain tries to label me as some sort of luddite, which really confuses them since, in my circle of friends/family, as I'm the go-to guy for technical problems. They assume I live on Facebook. I've never even had an account on Facebook, and honestly believe we'd all be better off if the whole site was shut down.
