-
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
Build a Roslyn-based parser for the Code First model #11659
Comments
As we have often discussed, the hardest part here is incorporating configuration code in OnModelCreating. We may be able to get "good enough" by building an interpreter for said code. Additional benefits are likely faster design-time ops (no need to build/load). |
@anpete Yeah, that's what I was thinking. We can recognize common patterns and I think get to a place where most people can use it, even if they need to comply a little bit to a well-known way of doing things. |
@ajcvickers Agreed. I think one first step is to de-couple CF from reflection. This should be pretty straight-forward - introduce an abstraction for CF metadata consumption. |
I bet @smitpatel can write this all in 1 line of code :) |
Something that needs to be watched out for with the real-time migrations would be data loss. You could quickly screw up your dev data without a way to either back out the change or disable this ability. |
If you are in the mood for building a parser please see this.... Just wishful thinking on my part but perhaps one day it will come to pass! |
Note from triage: Can of worms. |
To facilitate tooling/AOT scenarios such as:
It doesn't have to be a perfect parser for many of these scenarios. That is, it does not need to be able to fully recreate the runtime model, it just needs enough information to identify entities and database structure.
Other ideas for things to build on encouraged--please post in comments.
The text was updated successfully, but these errors were encountered: