Tools: Honor launchSettings.json

[bricelam]

The CLI added support for launchSettings.json in dotnet/cli#6617. Unfortunately, it only works with dotnet run and thus doesn't light up in our tooling.

If we want to honor launchSettings.json (particularly environment variables and command line arguments) in our tools, we'll have to look for and parse the file ourselves.

If we do this, we should also remove our existing logic that defaults the ASPNETCORE_ENVIRONMENT variable to Development.

[ajcvickers]

@danroth27 @DamianEdwards @Eilon @divega It would be great to have launchSettings.json be something that would work when using EF tooling. However, we're not going to try to hack this in by trying to parse the file in our own code. Do you guys see this as something we should push the CLI team to support? If so, we'll file an issue for it in dotnet/cli.

[ajcvickers]

@divega to file an issue on CLI side.

[divega]

We need a reusable component that dotnet run, VS and us can use.

[divega]

Filed https://github.com/dotnet/cli/issues/9730.

[divega]

@mlorbetske is now tracking this in his list. Clearing up fields to decide what to do with this issue.

[ajcvickers]

See also #22190--we should do this at the same time.

[kewur]

would love to be able to pass in the profile in launchSettings that has the environment variables rather than setting them in the terminal myself.

[Bykiev]

Hi, is any estimates when it'll be fixed?

[enrij]

Just found out that this tip allows firing any dotnet ef command with -- --launch-profile YourProfile and it works perfectly. I just tested it out with dotnet ef migrations script.

Hope it helps