-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Design: Public API to instantiate DbContext classes #7050
Comments
If we do, we should add it to 1.0.3 as well. |
@Eilon @ajcvickers Do we want to try and get this into 2.0.0-preview1 too? The work for |
(and possibly 1.0.4 & 1.1.2 so Scaffolding doesn't have to condition it on version) |
@bricelam Without this, what is broken? When you say "Scaffolding" I'm not sure which "Scaffolding" that is--reverse engineering, or asp.net scaffolding? Why would we put it in 1.0.4/1.1.2? What is broken there that this would fix? |
The Scaffoding repo. Anything they use a DbContext for is broken. ⭐️ I'll add back an overload to maintain compatibility in 2.0.0-preview1. ⭐️ |
@bricelam What's the priority of this for 2.0? |
We should do it so Scaffolding doesn't have to rely on internal API. Shouldn't be much work. |
Scaffolding is now using
DbContextOperations.CreateContext()
to instantiate contexts at design-time; however, this is an internal API.Model visualization may require the same functionality.
We should consider adding public API with this functionality.
cc @prafullbhosale
The text was updated successfully, but these errors were encountered: