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

How to deploy EF Migration at Release Time With Azure Pipelines #15228

Closed
BertCotton opened this issue Apr 1, 2019 · 2 comments
Closed

How to deploy EF Migration at Release Time With Azure Pipelines #15228

BertCotton opened this issue Apr 1, 2019 · 2 comments

Comments

@BertCotton
Copy link

Is there any documentation for doing EF Migration at release time? We are using the Azure Pipeline builds and could do it at build time, but that doesn't work because we need to to build once and deploy to each environment.
We do not want to do it at app runtime either. We want it to be a part of the release.

The only way that I've found to do it is to create a script 'dotnet ef migrations script..' during the build against a *.db file in the repo (which isn't ideal) and then ru nthat sql file during the release.

@BertCotton BertCotton changed the title How to deploy EF Migration at Releast Time With Azure Pipelines How to deploy EF Migration at Release Time With Azure Pipelines Apr 3, 2019
@ajcvickers
Copy link
Member

This is essentially a duplicate of #9841. @BertCotton There is some good information in the discussion on that issue, including a link to a post by Ben Day that should be quite useful.

@BertCotton
Copy link
Author

That's unfortunate. Maybe some good information but not a solution. Crazy that has been requested for over 6 months and still no solution. Definitely not something that would be production ready.

@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants