Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show how to use ASPNETCORE_ENVIRONMENT with Migrations #1050

Open
zuckerthoben opened this issue Oct 11, 2018 — with docs.microsoft.com · 0 comments
Open

Show how to use ASPNETCORE_ENVIRONMENT with Migrations #1050

zuckerthoben opened this issue Oct 11, 2018 — with docs.microsoft.com · 0 comments

Comments

Copy link

@zuckerthoben zuckerthoben commented Oct 11, 2018 — with docs.microsoft.com

The mentioned section misses to explain some (for me) important details you need if you want to use this approach:
The call Program.BuildWebHost is implicitly called with an ASPNETCORE_ENVIRONMENT setting of "development". That means that if you read the connection string from e.g. the appsettings inside AddDbContext, you need to have an appsettings file for this environment variable. Otherwise the root appsettings will be used, which means that you have to also copy the connection string to the database you want to use to this file. Otherwise this approach will fail, because it cant find the connection string.
Also in general the application needs to be able to start with the "development" env variable. If it for some reason does not build, you might face exceptions that you can't associate with the source of the problem.

My proposal:

  • Further explain the behavior of the mentioned section, including the implicit usage of "development" as env var
  • Perhaps give a short example on how to use this approach in practice

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.