Yeah, I’ve had to do that a few times lately. Really tweaked me when gcc transitioned things from warnings to errors.
Migrating from 4.6 to .NET Core.
Are we on .NET 7? No, only 8 is available here without unreasonable effort to backdate. Does the .NET 7 code run in 8 without mods? Yes, but that doesn’t change the hassle of talking endlessly about it.
Yeah, I’m in a bigger company, so I have the conversation with the local group, then the various other “Subject Matter Expert” groups that touch the same project in their own way, and just when I think I’m done having it there’s some group that submarines up and says “but we haven’t qualified our code to run on 8 so if you’re going to use it you’ll have to pay us to do the qualification, but we’re really busy so that’s going to be about 6 months before we can get to it…”
Yeah, I’ve had to do that a few times lately. Really tweaked me when gcc transitioned things from warnings to errors.
Are we on .NET 7? No, only 8 is available here without unreasonable effort to backdate. Does the .NET 7 code run in 8 without mods? Yes, but that doesn’t change the hassle of talking endlessly about it.
No. We weren’t. This one was about a decade ago, around the time they first released .NET Core.
Eh…ideally you’d have the conversation once, around what upgrade strategy to use, then execute on it. Upgrade yearly vs. ride out LTS windows. Etc.
Yeah, I’m in a bigger company, so I have the conversation with the local group, then the various other “Subject Matter Expert” groups that touch the same project in their own way, and just when I think I’m done having it there’s some group that submarines up and says “but we haven’t qualified our code to run on 8 so if you’re going to use it you’ll have to pay us to do the qualification, but we’re really busy so that’s going to be about 6 months before we can get to it…”