EF Core Tools Bug Bash

All the work we’ve done since last October finally shipped in version 1.0.0-msbuild3-final of the tools. There has been significant changes to the code including support for the new MSBuild-based (and CPS-based in VS 2017) projects. We would love to get as many people testing this out as we can (both team and community members alike).

If you find anything that isn’t working as expected, please submit an issue and (optionally) link to it from here.

What to use

With Visual Studio 2017 RC or .NET Core SDK 1.0 RC3, install the PMC tools by installing the Microsoft.EntityFrameworkCore.Tools package (like you would any other NuGet package). Use either version 1.0.0-msbuild3-final or 1.1.0-msbuild3-final depending on your version of the EF Core runtime.

Install dotnet ef by adding the following to your projects.

<ItemGroup>
  <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet"
                          Version="1.0.0-msbuild3-final" />
</ItemGroup>

Things to test

Variable	Values
Frameworks	.NETCoreApp, .NETStandard, .NETFramework, ✅ UAP, Xamarin, .NET Native
Platforms	AnyCPU, ✅ x86, x64, ARM
OS	✅ Windows, ✅ Linux, ✅ OSX
Project Types	Console, Web, ✅ UWP, Class Library, Runtime Component, .xproj
Tools	PMC, dotnet ef, ef.exe

Note: Struckthrough items are negative scenarios that should give good error messages.

• Different combinations of target and startup project types
• Interaction with VS
  • Adding, removing, and opening files
  • Setting window focus
  • Tab completion on PMC
• Help on dotnet ef
• ✅ .NET Core Runtime 1.1
• ✅ Cross-targeting
• ✅ Standalone apps

[bricelam]

@MarkusEgle It looks like that template doesn’t include the dotnet-ef tool. Add the following to your *.csproj.

<ItemGroup>
  <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet"
                          Version="1.0.0-msbuild3-final" />
</ItemGroup>

[bricelam]

@jamiewest We have the appropriate metadata in our nupkg, but NuGet hasn’t implemented the logic to handle it yet. This is a known issue, thanks!