Add .NET SDK 2.1.400, 2.1.401, 2.1.402

[zakaluka]

Description

3 new .NET SDKs are out, but currently the only way to use them with FAKE is with global.json. This adds supports directly in DotNet.Versions.

TODO

• New (API-)documentation for new features exist (Note: API-docs are enough, additional docs are in help/markdown)
  • Current fields have no additional documentation
• unit or integration test exists (or short reasoning why it doesn't make sense)
  • Could not find tests for previous SDK versions, not sure it needs testing.
• [] (if new module) the module has been linked from the "Modules" menu, edit help/templates/template.cshtml, linking to the API-reference is fine.
  • N/A
• [] (if new module) the module is in the correct namespace
  • N/A
• [] (if new module) the module is added to Fake.sln (dotnet sln Fake.sln add src/app/Fake.*/Fake.*.fsproj)
  • N/A
• Fake 5 API guideline is honored
  • follows current .NET SDK pattern.

[matthid]

Hey thanks a lot, I feel like mid-long term we might need a different approach considering the amount of versions... For now your change looks good.

[zakaluka]

If there was a way to list the contents of https://dotnetcli.azureedge.net/dotnet/, that may help dynamically generate the available versions.

[zakaluka]

Another option may be to parse the .NET SDK pages (https://www.microsoft.com/net/download/dotnet-core/2.2, https://www.microsoft.com/net/download/dotnet-core/2.1, etc.), find <h3> elements with an id starting with sdk-, and then creating entries for each entry found. FSharp.Data's HTML parser could be used to do that.

[zakaluka]

Ok, I think I finally got it - I believe that https://github.com/dotnet/core/blob/master/release-notes/releases.json contains the available releases.

version-sdk-display and version-sdk (if the former is unavailable) contain the version numbers that seems to be downloadable. Using those to create the Versions may make the most sense.

I'll try it out in a separate branch and you can review it to see if the approach makes sense.

[matthid]

@zakaluka Yes indeed, either something like that or just "pinning" major and minor version and adding the "patch" version as "int" parameter? Anyway this definitely looks good and I'm merging it on the next release.