Use consistent naming for .NET Core/Kestrel server settings in launchsettings.json

[dmvtech]

Sample information

All .NET Core samples here.

Describe the bug

For the dotnet core samples, the names for the core/Kestrel server are all over the place. Some match the actual project name, some are abbreviated so far that they do not make sense and many are completely wrong.

The launch settings for IIS Express are consistent. We should do the same for Core/Kestrel.

For example, we have something like:

    "DispatcherBot": {
      "commandName": "Project",
      "launchBrowser": true,
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      },
      "applicationUrl": "http://localhost:3978/"
    }

We don't need unique names for each sample, since the selected project is enough. Should have consistent and clear name for all samples using Core/Kestrel.

I don't know what name might be best to use, but some options:

• .NET Core <--my vote
• Kestrel
• Core (Kestrel)
• .NET Core (Kestrel)

And then would be something like:

    ".NET Core": {
      "commandName": "Project",
      "launchBrowser": true,
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      },
      "applicationUrl": "http://localhost:3978/"
    }

Additional context

https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-5.0

[dmvtech]

@cleemullins @EricDahlvang @mrivera-ms Any thoughts on which name to use?

[EricDahlvang]

Great idea! simple consistency trumps unnecessary complexity :)

I prefer ".NET Core", since I'm not even sure exactly what 'kestrel' is.

[mrivera-ms]

If we want to keep consistency with .NET Core apps, by default the Kestrel end points are created using the project name. Either way works. +1 on consistency across all samples.