2 ms·
> Do you consider yourself one of those confused people? Yes. I have never took place in a conversation about versioning problems in .Net where each person was
by marcosdumay 3y ago
> Do you consider yourself one of those confused people?
Yes. I have never took place in a conversation about versioning problems in .Net where each person wasn't talking about completely different things.
Anyway, I clearly remember nobody ever naming anything "framework" until the second or third stable version. And if there was such a thing, I would probably have heard, because MS was incredibly loud at the time.
It was retroactively renamed after it.
- WorldMaker 3y agoAs I recall it, even 1.0 was always referred to as .NET Framework. There was a million .NET "brands" from Microsoft when .NET Framework launched. .NET was the overall "initiative" and .NET Framework was only one in that "portfolio". Then Microsoft got bored with most of the other ".NET brands" and .NET Framework was last .NET standing. It wasn't until 2.0 or so that I recall people felt safe calling .NET Framework just ".NET" without feeling confused about other .NET branded things. Microsoft's own branding advice never dropped "Framework" from .NET Framework even deep into the 4.x timeframe so long divorced from "the initiative" and no other remaining uses of .NET as a brand.