-
Notifications
You must be signed in to change notification settings - Fork 103
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
Seed data #407
Seed data #407
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, thank you. We'll when you make the suggested changes.
Do you think that this PR covers this issue #64? |
I think it partially answers it - it sounds like in #64 they are trying to do traditional "Design time" migrations where they can just run migrations against their database or container using the ef core tools regardless of whether the app is running. However, the database container either doesn't exist or isn't accessible from local ef core tooling, which is why the example runs them during startup. I think this new doc shows them an alternate way of doing this, which they might be interested in - I don't think .NET Aspire supports traditional design time migrations at this point. |
Summary
Describe your changes here.
Fixes #Issue_Number (if available)
Internal previews