News for hackers. Stuff that matters.

A comment on The new ASP.NET Core 2.0 packages can no longer be used on .NET Desktop. Parent comment

Re:The new ASP.NET Core 2.0 packages can no longer be used o... by giancarlostoro on Tuesday May 09, 2017 @06:16AM (#14298832)
I always loved .NET Framework, but I agree, some of the names are confusing and don't make entire sense later on. Like if I want to code ASP .NET Core in SublimeText 3 the plugin mentions ASP .NET vNext, which I'm honestly not sure if that was just code for ASP .NET Core or some abandoned version of .NET (the fact it's not even in your post...) and it's sad. The only one's I know currently are:

* .NET Core - a new spin on .NET Framework for the cloud and such, not always compatible with .NET Framework but sometimes compatible. * .NET Framework (or "Full") - the .NET Framework we've known and loved, what was a few years ago merely known as .NET * .NET Standard - the bridge between the two, made after .NET Core so that they could break backwards compatibility to some extent, or they realized "whoops we gotta make a compatibility layer" or some other reason...

I'm not even sure what .NETfx is, nor what ASP .NET vNext was, and if it was just an alpha, all I know is in Sublime Text I don't have sane / easy options. On Visual Studio Code I can just install the "C#" plugin on the other hand and get going. It's not as good as Visual Studio's IntelliSense though.

One nice thing about .NET Core is the ability to develop from any platform and to deploy to any platform. .NET Framework needed Mono for that, I wonder how much of .NET Core will become Mono Core or something similar (if at all?).

[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by piaste on Tuesday May 09, 2017 @06:28AM (#14298865)
".NETfx" is a common shorthand for .NET Framework. And that was perhaps the worst possible post to use a common shorthand.
[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by giancarlostoro on Tuesday May 09, 2017 @07:46AM (#14299165)
So am I right in assuming .NETfx and .NET Full are the same? Or... Yeah I still love .NET not a fan of the weird transition phase, I can't help but think that Core should of been stuck into Alpha for this time frame, but then people would complain it's ready for prime.
[ Parent | on HN ]
Re:The new ASP.NET Core 2.0 packages can no longer be used o... by WorldMaker on Tuesday May 09, 2017 @12:05PM (#14301157)
Plus, .NET Core is the first developed openly on GitHub as open source, so you get the teething pains of seeing how all the sausage is made. On the one hand this is great to see so much transparency and open source collaboration. On the other hand, for a lot of .NET veterans used to only hearing about .NET updates maybe once every three years at a well rehearsed developer conference, the world of open source transparency is definitely a fire hose of information updates and that makes for a very rough transition.
[ Parent | on HN ]