We have a(n enterprise) product that uses .NET 4.x for the UI, and I've explored moving to current .NET, however: * Supporting some older OSes and requiring le

We have a(n enterprise) product that uses .NET 4.x for the UI, and I've explored moving to current .NET, however: * Supporting some older OSes and requiring less system base updates is key * There's a priority to keep installation size (relatively) small * There's a (higher-up) notion of "if it works, why change it" On top of that, some technical issues I've encountered (since resolved) and gave up on upgrading were: * Up until relatively recently there was no "single executable" deployment * For some part of Core's lifetime you had this weird deployment of DLL-run-by-EXE that's a dealbreaker for the software's security boundaries & requirements * Huge executable size, until recently where trimming unused framework code was added There was also some period of time where the .NET party line was "WPF is legacy, we don't support it on modern .NET" and our UI is already built in WPF. We couldn't move to something like WinUI due to supporting Windows <10 and even then, WinUI 3 increases your deployment executable's size by a lot. Thankfully they added WPF support in .NET 8/9.