4 ms·

There is no .NET Core or .NET Framework since .NET 5.0 in 2020. Maybe you mean ASP.NET Core, but then there is no ASP.NET Framework so the comment still does no

There is no .NET Core or .NET Framework since .NET 5.0 in 2020. Maybe you mean ASP.NET Core, but then there is no ASP.NET Framework so the comment still does not make sense to me. The vulnerable component is ASP.NET Core, which did not change name when .NET dropped the Core name to distinguish it from legacy ASP.NET. --- edit: cut here - the sentence below is incorrect! --- If somehow you were still using legacy ASP.NET / Framework 4.8 etc, you have much bigger problems - legacy ASP.NET has been unsupported since 2022 so will definitely not be receiving security updates.

paulirwin 1y ago
The last sentence is not correct. ASP.NET is part of .NET Framework which is still supported by nature of being included with Windows, and follows its support lifecycle. https://dotnet.microsoft.com/en-us/platform/support/policy/aspnet https://dotnet.microsoft.com/en-us/platform/support/policy/a... This is, IMO, a bad thing, and Microsoft needs to break this chain at some point, at least for ASP.NET. But, it is still technically supported.
- ninjaoxygen 1y ago
  Yes, you are right, if you are on 5.0+, however the 4.x stuff is definitely out of support. Sorry, I did not know they had actually brought non-Core ASP.NET forward into 5.0+, but it makes sense given how much of .NET Framework they continued support for and how much ASP.NET and Forms stuff is still around in enterprise with no budget for bringing it forward. Totally agree with breaking the chain though, we moved to Core around 2.0 and never looked back, as an ecosystem it is so much better.
  - Hawxy 1y ago
    > however the 4.x stuff is definitely out of support [...] Sorry, I did not know they had actually brought non-Core ASP.NET forward into 5.0+ None of this is true, you've gotten yourself very confused. The only real change with .NET 5 was the "Core" name being dropped and the Mono runtime being merged in. .NET Framework 4.x is still around and is still fully supported for legacy applications.
- jve 1y ago
  There is still modern MS product (Dataverse) that requires to code plugins in .NET Framework 4.6.2: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/write-plug-in?tabs=pluginbase#iplugin-interface https://learn.microsoft.com/en-us/power-apps/developer/data-... And there is currently no official other supported version supported like .NET Framework 4.8 or simply .NET
calebt3141 1y ago
> If somehow you were still using legacy ASP.NET / Framework 4.8 etc, you have much bigger problems - legacy ASP.NET has been unsupported since 2022 so will definitely not be receiving security updates. I don't think this is correct: .NET 4.8 / 4.8.1 shows does not have an end of support date set: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-framework https://dotnet.microsoft.com/en-us/platform/support/policy/d... Also ASP.NET MVC 5 does not have an end of support date set: https://dotnet.microsoft.com/en-us/platform/support/policy/aspnet https://dotnet.microsoft.com/en-us/platform/support/policy/a... There are plenty of apps out there were there is no feasible upgrade path to .NET Core / .NET 9, so I imagine MS will continue to support these for a very long time. Note that the VB6 runtime is still supported in all Windows operating systems: https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6-support-policy https://learn.microsoft.com/en-us/previous-versions/visualst...
- ninjaoxygen 1y ago
  Yes, you're right, the last sentence is definitely a mistake on my part, I should have written less! Thanks for the links, paulirwin's sibling response is helpful too. We had code using WCF and AppDomains that were always out of scope for .NET Core. WCF has a Core replacement now that is not quite one-for-one but AppDomains will never be supported in .NET Core / .NET 5.0+ and would indeed have to stay on 4.8 / 4.8.1 if they were still running.
MarkSweep 1y ago
.NET Core got renamed .NET in version 5. .NET Framework is still used as the name of the classic version of .NET that comes with Windows. See here: https://learn.microsoft.com/en-us/dotnet/fundamentals/implementations https://learn.microsoft.com/en-us/dotnet/fundamentals/implem...
SomeUserName432 1y ago
> There is no .NET Core or .NET Framework since .NET 5.0 in 2020 There is both a .Net and a .Net Framework, with the latest .net framework update being about ~3 years old, years after .net 5 was released. I'm finally working on migrating (migrate, not upgrade) from .Net framework 4.7.2 to .Net 9 It was a previously impossible / very difficult due to strong dependencies on functionality which only existed in .Net Framework. With the continued development of Winforms on .Net 9+, it finally made sense to start migrating over.
pjmlp 1y ago
Yes, there is, because Microsoft naming sucks, and making the distiction between .NET Core and .NET Framework is the only way to actually explain modern .NET to most folks without background on .NET. Additionally the mistake to rename .NET Core as .NET is the main reason many people still think .NET is Windows only.
- pverheggen 1y ago
  Well they did have a valid reason for a rename, .NET 5.0's announcement coincided with discontinuing Mono and Xamarin, and uniting the non-Windows .NET flavors under a single platform. They also planned to iterate more rapidly and add APIs beyond .NET Standard. But yes, choosing ".NET" as the new name was a bad idea, since now when someone says .NET you have no idea if they are referring to the modern runtime, or its various generations collectively.
  - orphea 1y ago
    I, for one, think dropping the "Core" suffix (absolutely dumb naming) was the right thing. Yes, it might have created some confusion with the old .NET aka .NET Framework but I hope it's temporary. It's been five years of .NET-no-suffix and nine of it being cross-platform. At some point people should just educate themselves and stop thinking that .NET is somehow Windows only.
    - pjmlp 1y ago
      Good luck with that, the .NET team keeps referring this is a recurring problem trying to get new users that rather pick something else for their startups or teaching curriculum, just go listen to .NET podcasts where well known figures got interviewed.

paulirwin 1y ago

The last sentence is not correct. ASP.NET is part of .NET Framework which is still supported by nature of being included with Windows, and follows its support lifecycle. https://dotnet.microsoft.com/en-us/platform/support/policy/aspnet https://dotnet.microsoft.com/en-us/platform/support/policy/a... This is, IMO, a bad thing, and Microsoft needs to break this chain at some point, at least for ASP.NET. But, it is still technically supported.

ninjaoxygen 1y ago
Yes, you are right, if you are on 5.0+, however the 4.x stuff is definitely out of support. Sorry, I did not know they had actually brought non-Core ASP.NET forward into 5.0+, but it makes sense given how much of .NET Framework they continued support for and how much ASP.NET and Forms stuff is still around in enterprise with no budget for bringing it forward. Totally agree with breaking the chain though, we moved to Core around 2.0 and never looked back, as an ecosystem it is so much better.
- Hawxy 1y ago
  > however the 4.x stuff is definitely out of support [...] Sorry, I did not know they had actually brought non-Core ASP.NET forward into 5.0+ None of this is true, you've gotten yourself very confused. The only real change with .NET 5 was the "Core" name being dropped and the Mono runtime being merged in. .NET Framework 4.x is still around and is still fully supported for legacy applications.
jve 1y ago
There is still modern MS product (Dataverse) that requires to code plugins in .NET Framework 4.6.2: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/write-plug-in?tabs=pluginbase#iplugin-interface https://learn.microsoft.com/en-us/power-apps/developer/data-... And there is currently no official other supported version supported like .NET Framework 4.8 or simply .NET

calebt3141 1y ago

> If somehow you were still using legacy ASP.NET / Framework 4.8 etc, you have much bigger problems - legacy ASP.NET has been unsupported since 2022 so will definitely not be receiving security updates. I don't think this is correct: .NET 4.8 / 4.8.1 shows does not have an end of support date set: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-framework https://dotnet.microsoft.com/en-us/platform/support/policy/d... Also ASP.NET MVC 5 does not have an end of support date set: https://dotnet.microsoft.com/en-us/platform/support/policy/aspnet https://dotnet.microsoft.com/en-us/platform/support/policy/a... There are plenty of apps out there were there is no feasible upgrade path to .NET Core / .NET 9, so I imagine MS will continue to support these for a very long time. Note that the VB6 runtime is still supported in all Windows operating systems: https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6-support-policy https://learn.microsoft.com/en-us/previous-versions/visualst...

ninjaoxygen 1y ago
Yes, you're right, the last sentence is definitely a mistake on my part, I should have written less! Thanks for the links, paulirwin's sibling response is helpful too. We had code using WCF and AppDomains that were always out of scope for .NET Core. WCF has a Core replacement now that is not quite one-for-one but AppDomains will never be supported in .NET Core / .NET 5.0+ and would indeed have to stay on 4.8 / 4.8.1 if they were still running.

MarkSweep 1y ago

.NET Core got renamed .NET in version 5. .NET Framework is still used as the name of the classic version of .NET that comes with Windows. See here: https://learn.microsoft.com/en-us/dotnet/fundamentals/implementations https://learn.microsoft.com/en-us/dotnet/fundamentals/implem...

SomeUserName432 1y ago

> There is no .NET Core or .NET Framework since .NET 5.0 in 2020 There is both a .Net and a .Net Framework, with the latest .net framework update being about ~3 years old, years after .net 5 was released. I'm finally working on migrating (migrate, not upgrade) from .Net framework 4.7.2 to .Net 9 It was a previously impossible / very difficult due to strong dependencies on functionality which only existed in .Net Framework. With the continued development of Winforms on .Net 9+, it finally made sense to start migrating over.

pjmlp 1y ago

Yes, there is, because Microsoft naming sucks, and making the distiction between .NET Core and .NET Framework is the only way to actually explain modern .NET to most folks without background on .NET. Additionally the mistake to rename .NET Core as .NET is the main reason many people still think .NET is Windows only.

pverheggen 1y ago
Well they did have a valid reason for a rename, .NET 5.0's announcement coincided with discontinuing Mono and Xamarin, and uniting the non-Windows .NET flavors under a single platform. They also planned to iterate more rapidly and add APIs beyond .NET Standard. But yes, choosing ".NET" as the new name was a bad idea, since now when someone says .NET you have no idea if they are referring to the modern runtime, or its various generations collectively.
- orphea 1y ago
  I, for one, think dropping the "Core" suffix (absolutely dumb naming) was the right thing. Yes, it might have created some confusion with the old .NET aka .NET Framework but I hope it's temporary. It's been five years of .NET-no-suffix and nine of it being cross-platform. At some point people should just educate themselves and stop thinking that .NET is somehow Windows only.
  - pjmlp 1y ago
    Good luck with that, the .NET team keeps referring this is a recurring problem trying to get new users that rather pick something else for their startups or teaching curriculum, just go listen to .NET podcasts where well known figures got interviewed.