4 ms·

> .Net that was renamed into .Net Framework This is not correct. .NET Framework was named Framework from 1.0. The only time something was renamed is .NET 5 whi

by orphea 3y ago

> .Net that was renamed into .Net Framework This is not correct. .NET Framework was named Framework from 1.0. The only time something was renamed is .NET 5 which came after .NET Core 3.1. > We also have a bunch of confused people without any reason, because all of this is as clear as water. It's funny you say that. Do you consider yourself one of those confused people? :)

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 ago
  As 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.
borissk 3y ago
Haha, the burn. I remember back in the day - around 2001 - Microsoft thought it will center all their products around Web Services and call them .NET. Windows .NET Server was the supposed name for Server 2003. In the end a few things came out of it: Visual Studio .NET, .NET (the framework), VB.NET, ASP.NET. https://en.wikipedia.org/wiki/Microsoft_.NET_strategy https://en.wikipedia.org/wiki/Microsoft_.NET_strategy

by orphea 3y ago

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 ago
As 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.

borissk 3y ago

Haha, the burn. I remember back in the day - around 2001 - Microsoft thought it will center all their products around Web Services and call them .NET. Windows .NET Server was the supposed name for Server 2003. In the end a few things came out of it: Visual Studio .NET, .NET (the framework), VB.NET, ASP.NET. https://en.wikipedia.org/wiki/Microsoft_.NET_strategy https://en.wikipedia.org/wiki/Microsoft_.NET_strategy