[huzaif]

Publish your apps without .net core (--no-self-contained) and install/manage runtimes as you usually would.

If you have thousand apps, you probably also have a CI/CD system and you can gain fine grained control on your runtime management needs with .net build/publish.

MS does quite a few things poorly but they have done a solid job of operating in large enterprises.

[ocdtrekkie]

"Publish your apps" isn't the issue: I support a lot of applications I don't build or have the source code for. And they may be on my network for over ten years.

The problem is if developers are publishing self-contained apps with .NET Core, IT staff will be up a creek on vulnerability mitigation. While being able to pin specific .NET Core versions is nice for developers, being able to require the most current .NET Core version be used is important for IT staff who have to support these applications.

[hackerfromthefu]

I'm expecting as this issue plays out, there will be a way to inject an updated framework to an existing app with a utility tool. Probably first party but definitely third party.

[jiggawatts]

> you probably also have a CI/CD system

Or more realistically, dozens of CI/CD systems, covering less than a third of the applications.