Multiple projects and migrations about entityframework.docs HOT 5 CLOSED

dupe of dotnet/efcore#2679 ?

from entityframework.docs.

Yeah, I saw that one, but I wasn't sure if that was exactly the case, even if it's similar.

My first instinct is to just create a symlink to Startup.cs from the data access project to the project main, but that's just a hack. Instead, I began looking at the EF code, but then I wondered why it got ugly when @bricelam looked at, but then I realized I didn't understand nearly enough to even properly evaluate "ugly" so I stopped.

So thinking out loud here, if dnu/dnx knows that there is another project because it's listed in the dependencies, couldn't EF ask dnu/dnx about that? Or does dnu/dnx just keep that information to itself? Anyway, I love this stuff!

from entityframework.docs.

The Startup could not be found error should be resolved (in the nightly builds) by dotnet/efcore#3327.

We need dotnet/efcore#2679 to fully enable the scenario, and when it's in the commands would look something like this.

cd src\Business
dnx ef migrations add MyMigration --startupProject MyWebApplication

from entityframework.docs.

We should have some documentation about how to get EF to work when start-up and context are in different projects.
Points to include:

• How to set up startup
• How to run ef commands

from entityframework.docs.

Consolidating with #204

from entityframework.docs.