Add schema in launchSettings.json files

[sebastienros]

Fixes #38120

Complementary to SchemaStore/schemastore#2507

[JamesNK]

I'm not sure if this is the right approach. appsettings.json, for example, has the schema automatically inferred by VS and VS code.

Change to the VS code extension for that: dotnet/vscode-csharp#4280. There was a similar change in VS.

Do we want the schema added to these files, or should it be consistent with what appsettings.json does?

[sebastienros]

@JamesNK it's nice that the tooling can infer the schema, but I don't think it's contradicting this PR. If someone uses another tool, let's say Rider, or VS for MAC (not sure it does it too). And assuming adding the schema in the templates don't conflict with the tooling.

One template already had the reference, so if we decide to not add the schema then I will remove it from there (

aspnetcore/src/ProjectTemplates/Web.ProjectTemplates/content/WebApi-CSharp/Properties/launchSettings.json

Line 2 in 9127115

"$schema": "https://json.schemastore.org/launchsettings.json",

)

In any case we can also ponder if launchSettings support should be added to tooling too.

[JamesNK]

Another thing to consider is the schema file that VS generates if one isn't present. I tested deleting the file and restarting VS, and the newly generated launchSettings.json doesn't have a $schema property.

[sebastienros]

Should we just discard this PR then and assume that the issue is fixed as we updated the schema to add more properties?

I see that the changes I pushed on the schema are actually already working in VS, and it's inferred:

[JamesNK]

Should we just discard this PR then and assume that the issue is fixed as we updated the schema to add more properties?

Yeah, I think so. Although it sounds like one launchSettings.json is specifying the schema. Remove it from that one for consistency?

[sebastienros]

Found 4 files with it, 2 sample and 2 templates

[sebastienros]

@JamesNK GTG?

[sebastienros]

@dotnet/aspnet-build please merge