As Craig said Code First is a misnomer.

You will be able to import existing models from an existing database just as you can today with Code First. You just won't get a designer at least initially. That's not to say that they won't add a designer later.

The reasoning for all this is that vNext will only have dbContext which removes the secondary mapping layer that (the EDMX model that kept logical and physical modal separate) so doing a designer is a lot more complex directly off source code and the various provider conventions that EF code first provides. But not impossible.

Frankly though the designers have also been very limited in comparison what you can do in code or even with basic attributes. While i like to see things visually too I've found that I don't miss the designer even in hideously complex models (which you should try to break out into simpler silos anyway if at all possible).


+++ Rick ---



>Unless they address the limitation where you can't generate a code-first model from the db incrementally, it's going to be a big mistake. Code-first with a legacy database under somebody else's control is a nightmare currently.
>
>>Yup. That's why I said to not bother with it. I heard the reasoning directly from Rowan, but forgot the specifics. It made sense at the time.
>>
>>>I forgot my source, but they're removing the designer. I do think that is a poor choice because the designer definitely has its place.