The --launch-profile option of `dotnet run` and `dotnet watch run` should fallback to a case-insensitive match if a case-sensitive match isn't found

Today, dotnet run --launch-profile profilename and dotnet watch run --launch-profile profilename are case-sensitive and if a matching profile is not found in launchSettings.json an error message is displayed but the project is run anyway, e.g.:

launchSettings.json

{
  "profiles": {
    "http": {
      "commandName": "Project",
      "dotnetRunMessages": true,
      "launchBrowser": true,
      "applicationUrl": "http://localhost:5130",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      }
    },
    "HTTPS": {
      "commandName": "Project",
      "dotnetRunMessages": true,
      "launchBrowser": true,
      "applicationUrl": "https://localhost:7175;http://localhost:5130",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      }
    }
  }
}

$ dotnet run --launch-profile https
The launch profile "https" could not be applied.
A profile with the specified name could not be found or is not a valid JSON object.
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://localhost:5000

It would be more user-friendly in cases like this to simply fallback to a case-insensitive match if a case-sensitive match is not found first.

[baronfel]

Thanks for the help narrowing down on this. I put it in the 7 backlog and we’ll get to it as we can! I do think this would be a good area for @nagilson after he tackles the various Release configuration/RID inference changes for 7 if nothing else crazy pops up.

[baronfel]

What about something like this:

• if the name is case-insensitively unique (i.e. http in your image above), then accept any case
• if the name has case-sensitive variants, require case-sensitive matches or else error
• completions always suggest the user-entered spellings exactly