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.