Microsoft urges devs to migrate away from .NET Core 3.1 ASAP
-
Microsoft has urged developers still using the long-term support (LTS) release of .NET Core 3.1 to migrate to the latest .NET Core versions until it reaches the end of support (EOS) next month.
We're still good with .NET 1.1 though, right?
Or 2.0 if you like LINQ?
-
Microsoft has urged developers still using the long-term support (LTS) release of .NET Core 3.1 to migrate to the latest .NET Core versions until it reaches the end of support (EOS) next month.
We're still good with .NET 1.1 though, right?
Or 2.0 if you like LINQ?
Kent Sharkey wrote:
Or 2.0 if you like LINQ?
Except LINQ wasn't introduced until 3.5. ;P
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Kent Sharkey wrote:
Or 2.0 if you like LINQ?
Except LINQ wasn't introduced until 3.5. ;P
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Bah! Spoiled my own joke. Alas. What was I thinking of then? Dur… generics?
TTFN - Kent
-
Microsoft has urged developers still using the long-term support (LTS) release of .NET Core 3.1 to migrate to the latest .NET Core versions until it reaches the end of support (EOS) next month.
We're still good with .NET 1.1 though, right?
Or 2.0 if you like LINQ?
Kent Sharkey wrote:
We're still good with .NET 1.1 though, right?
It's still the preferred .net for NT4 applications. :-\
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius
