EF Core 1.1.0 Migrations on other servers (not development)
<p>When development is finished and TFS (VSTS) takes over. The build completes successfully and the artifact directory contains the published website via a build definition. The Release Manager is then triggered, and takes over and creates a website in an environment, the website files are copied to the environment and the website started. All good so far.</p>

<p>Missing the Database migration steps here...</p>

<p>Now someone starts the server and it fails because the database has not been migrated. How do we do that? The EF Tools were not copied to that environment, in fact we can't even run dotnet.exe because the core sdk has not been deployed onto that environment either. so even if we had the tools, we can't execute them.</p>

<p>In EF 6.x it was easy cause we could just copy migrate.exe as part of the artifacts, and run that on the environment after the files were copied. As I understand it, the EF Tools are now a DLL (ef.dll) that has to be run by dotnet.exe. Does this mean that all web servers now need Core SDK to perform migrations?</p>

<p>Other details about my project setup:
asp.net.core application being deployed onto a QA server for testing. This is not a dev box, does not have VS2015 installed, does not have Core SDK installed.</p>

<h3>Update:  EF.EXE is part of preview3 and 4.</h3>

<p>This solves the requirement for "dotnet.exe" being installed.  I can copy that into the artifacts drop like I used to with migrate.exe.  Is this the proposed solution by the EF Team?</p>