Altered EF Core Migrations tutorial to ensure that API waits for the migrations to complete #3846
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Altered the code in the solution to use the WaitForCompletion() method to ensure that the API doesn't start until the migrations are completed. Also corrected the code line numbers to ensure the correct highlighting and upgraded to .NET Aspire 9.3.1.
This PR goes with the following PRs in the example repo and should be merge at the same time:
Upgrade solution to aspire 9.3 #9
Upgraded to .NET Aspire 9.3.1 #10
Fixes #3715
Internal previews