The .NET Core 2 Wave

Re:The .NET Core 2 Wave by blauditore on Monday January 23, 2017 @09:25AM (#13462310)

I just looked up what exactly .NET Core is and landed on the installation guide page[1], which includes installation videos for Windows and Mac OS. It's quite funny how they, uhm, adapted those to target audiences... :)

[1]: www.microsoft.com/net/core

[ Parent | on HN ]

Re:The .NET Core 2 Wave by wongarsu on Monday January 23, 2017 @09:44AM (#13462452)

You also don't want to miss the Ubuntu video.

[ Parent | on HN ]

Re:The .NET Core 2 Wave by memsom on Tuesday January 24, 2017 @04:31AM (#13469944)

Kendra Havens is a hilariously funny in those videos. She does a really good job of making setting everything up seem like a whole load of fun rather than a chore.

[ Parent | on HN ]

Re:The .NET Core 2 Wave by blauditore on Monday January 23, 2017 @11:14AM (#13463180)

Huh, didn't see this. Where can I find it?

[ Parent | on HN ]

Re:The .NET Core 2 Wave by wongarsu on Monday January 23, 2017 @11:49AM (#13463522)

In the Linux tab of the instructions there are tabs for various Linux distributions (each with slightly different instructions). The instructions for Ubuntu are the only ones with a video.

[ Parent | on HN ]

Re:The .NET Core 2 Wave by blauditore on Monday January 23, 2017 @02:00PM (#13464864)

Ah thanks, that's hilarious!

[ Parent | on HN ]

Re:The .NET Core 2 Wave by vetinari on Monday January 23, 2017 @10:45AM (#13462933)

Speaking of target audiences using non-Windows systems... how does their versioning work there?

The version labeled 1.0.3 TLS is dotnet-dev-osx-x64.1.0.0-preview2-003156.pkg (1.0.0? preview?)

The version labeled 1.1 is dotnet-dev-osx-x64.1.0.0-preview2-1-003177.pkg (again: 1.0.0 preview?)

The linux packages have similar pattern.

[ Parent | on HN ]

Re:The .NET Core 2 Wave by dsp1234 on Monday January 23, 2017 @12:03PM (#13463637)

"Preview 2" is the tooling version (command line tools). The tools (such as the dotnet command and related binaries) are versioned separately from the framework itself.

This allows the team the ability to release new tooling versions (bugfix to the donet command for example), without having to print a new framework version. Same for updating the framework vs the tooling.

On the one hand, it's annoying to keep track of so many versions. On the other hand, it's also annoying to be forced to run a framework update when the only thing that's changed is a command line tool, which may or may not be important to a specific organizations development pipeline.

[ Parent | on HN ]

Re:The .NET Core 2 Wave by vetinari on Monday January 23, 2017 @01:10PM (#13464310)

Thanks for the explanation, makes sense.

[ Parent | on HN ]

Re:The .NET Core 2 Wave by socrates666 on Monday January 23, 2017 @11:02AM (#13463071)

Microsoft adapted this versioning http://semver.org/ standard.

So, 1.0.0-previewX < 1.0.0.

Semantically this should be read as "1.0.0-previewX is preview X of version 1.0.0"

[ Parent | on HN ]

Re:The .NET Core 2 Wave by vetinari on Monday January 23, 2017 @11:27AM (#13463313)

Then their own labeling does not reflect the versions indicated in the filenames.

[ Parent | on HN ]

Re:The .NET Core 2 Wave by limeyx on Wednesday January 25, 2017 @12:16PM (#13483375)

At least as of a month or so ago it was plainly obvious that Mac is a third level supported platform here.

[ Parent | on HN ]