It's worse on less formal communication, but shorthand "We're targeting .NET" might mean "We're targeting .NET (Standard)" (Which works on both Framework and u

It's worse on less formal communication, but shorthand "We're targeting .NET" might mean "We're targeting .NET (Standard)" (Which works on both Framework and used to be Core / current .NET) "We're targeting .NET (Framework)" (Used to be shortened to .NET) "We're targeting .NET" (Formerly .NET Core) / (6/7/8/9), current recomendation being to call this one just .NET (But not always respected, and not retroactively applied If legacy wasn't a thing, there wouldn't be much trouble, but since many libraries and some functionality does get backported, you might be stuck with documentation doing any of them, maybe even inconsistently