I suggest you ...

Make it possible to choose ASP.NET Core Environment for Migrations when publishing to Azure

Currently when publishing to Azure with an EF Core DBContext there is no possiblity to choose the ASPNETCORE_ENVIRONMENT to use for creating and applying the migrations from the dialog. But if you are using different Database providers for different scenarios this Distinguishment becomes crucial. In my case it was a local MySQL DB and a Azure SQL DB. The workaround I used was to use the Package Manager console, apply the migration to the Azure SQL DB and then publish the application. But it was quite cumbersome and I do not think that it fits well with the Idea of easy deployment to cloud services.

3 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Björn Höper shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base