3 ms·

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 l

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

3 ms·

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 l

by paulirwin 1y ago

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