You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2020. It is now read-only.
I've merged in the changes from the RTM upgrade, however I'm now having some weirdness with the Azure Websites instance (locally everything works fine).
When deploying to Azure Websites I can't use the Connection Strings section in Azure Websites Application Settings, instead I need to add a "Data:DefaultConnection:ConnectionString" App setting key with the connection string. This could be the faulty of Azure and RTM, but I'm not sure.
When the database finally does connect, I can't migrate or seed it. Instead it appears to fall back to the localdb connection string. Not sure whats happening here. I connected my local api to the azure db and the db creation and seeding worked fine. So something in the azure websites stuff I suspect.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey @igorgoldobin, cc/ @adamstephensen
I've merged in the changes from the RTM upgrade, however I'm now having some weirdness with the Azure Websites instance (locally everything works fine).
When deploying to Azure Websites I can't use the Connection Strings section in Azure Websites Application Settings, instead I need to add a "Data:DefaultConnection:ConnectionString" App setting key with the connection string. This could be the faulty of Azure and RTM, but I'm not sure.
When the database finally does connect, I can't migrate or seed it. Instead it appears to fall back to the localdb connection string. Not sure whats happening here. I connected my local api to the azure db and the db creation and seeding worked fine. So something in the azure websites stuff I suspect.
The text was updated successfully, but these errors were encountered: