9 ms·
Seems like it makes the problem worse because you are then tied to a specific version at time of publishing and need to republish to get any framework patches.
by Jwarder 4y ago
Seems like it makes the problem worse because you are then tied to a specific version at time of publishing and need to republish to get any framework patches.
https://learn.microsoft.com/en-us/dotnet/core/deploying/runtime-patch-selection https://learn.microsoft.com/en-us/dotnet/core/deploying/runt...
- foepys 4y agoIndeed. Microsoft identified this as a problem as well and pushes .NET security patches via Windows Update nowadays. When using self-contained apps, you won't get these patches.
- easton 4y ago.NET Core security patches aren't pushed via Windows Update, only .NET Framework (since it's built into Windows). Unless something changed recently?
- vel0city 4y agoYou missed how there effectively isn't a .NET Core/.NET Framework delination anymore. It is just .NET, and .NET gets security patches from Windows Update.
- pjmlp 4y ago.NET Core got renamed into .NET as of .NET 5, and it is still quite relevant to make a difference, plenty of people still don't get it.
- seritools 4y agoIf "Microsoft Update" is enabled in the Windows Update settings, you do get .NET Core updates: https://devblogs.microsoft.com/dotnet/net-core-updates-coming-to-microsoft-update/ https://devblogs.microsoft.com/dotnet/net-core-updates-comin...
- easton 4y agoNews to me! I always deploy .NET 5/6 stuff on Linux, explains why I'm out of the loop. Thanks!
- AlfeG 4y agoIt's same issue as deploying containers.