5 ms·

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 f

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

wongarsu 10y ago
You also don't want to miss the Ubuntu video.
- blauditore 10y ago
  Huh, didn't see this. Where can I find it?
  - wongarsu 10y ago
    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.
    - blauditore 10y ago
      Ah thanks, that's hilarious!
- memsom 10y ago
  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.
vetinari 10y ago
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.
- socrates666 10y ago
  Microsoft adapted this versioning http://semver.org/ 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"
  - vetinari 10y ago
    Then their own labeling does not reflect the versions indicated in the filenames.
- dsp1234 10y ago
  "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.
  - vetinari 10y ago
    Thanks for the explanation, makes sense.
limeyx 10y ago
At least as of a month or so ago it was plainly obvious that Mac is a third level supported platform here.

wongarsu 10y ago

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

blauditore 10y ago
Huh, didn't see this. Where can I find it?
- wongarsu 10y ago
  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.
  - blauditore 10y ago
    Ah thanks, that's hilarious!
memsom 10y ago
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.

vetinari 10y ago

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.

socrates666 10y ago
Microsoft adapted this versioning http://semver.org/ 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"
- vetinari 10y ago
  Then their own labeling does not reflect the versions indicated in the filenames.
dsp1234 10y ago
"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.
- vetinari 10y ago
  Thanks for the explanation, makes sense.

limeyx 10y ago

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