>You are clearly thinking about smaller projects. Yes, because that's the majority. You will probably not see another major upgrade from .NET to new-shiny-thi

>You are clearly thinking about smaller projects. Yes, because that's the majority. You will probably not see another major upgrade from .NET to new-shiny-thing in a decade or more, so you may as well take the extra time to do things right for .NET now, even for the largest projects. There have been multiple LTS's to target, and once you are over the initial Framework -> .NET "hurdle", upgrading from there should be much easier. >Larger projects can't survive a "stop the world" / "go async" project. I don't know how it would be fatal unless the company doesn't want to give you the time for it - either because it doesn't make financial sense or they haven't been convinced. .NET is certainly one of the easier languages to refactor with confidence. If it will never make financial sense, then I guess it'll go on to join the still-running COBOL projects, but that's an outlier.