Getting started wiki page steps don't seem to work on master branch.
https://github.com/aspnet/EntityFrameworkCore/wiki/getting-and-building-the-code
I can't get the .\build /t:Compile cmd to work on master, error is that the target doesn't exist.
Have no problems on release/2.2 branch.
Would be great to get this doc updated as I'd like to look at contributing something and without this working it seems all the projects in the sln fail to load.
.\build /t:Compile in PowerShellEF Core version: n/a
Database Provider: n/a
Operating system: Windows 10
IDE: Visual Studio 2017 15.latest, Visual Studio 2019 Preview latest
I agree that the wiki page is outdated. We will update it.
In the meantime,
To open solution in VS, you just need to do startvs.cmd EFCore.sln. (you can open any other solution file the same way).
startvs.cmd script will take care of restoring required packages and setting env variables appropriately for VS to work.
restore.cmd restores packages
build.cmd restore packages and build everything. (no packaging)
test.cmd should run all tests after building everything.
build.cmd -pack should produce nuget packages.
Hope this helps.
Thanks!
Updated https://github.com/aspnet/EntityFrameworkCore/wiki/Getting-and-Building-the-Code
Let us know if anything missing
Awesome. Thanks!
Ended up running into an issue building (both via cmd or in VS). Basically found I was getting the same "Duplicate assembly attribute" type exception as here: https://github.com/dotnet/cli/issues/4710
Deleted all obj and bin folders, clean and build then worked.
Most helpful comment
I agree that the wiki page is outdated. We will update it.
In the meantime,
To open solution in VS, you just need to do
startvs.cmd EFCore.sln. (you can open any other solution file the same way).startvs.cmdscript will take care of restoring required packages and setting env variables appropriately for VS to work.restore.cmdrestores packagesbuild.cmdrestore packages and build everything. (no packaging)test.cmdshould run all tests after building everything.build.cmd -packshould produce nuget packages.Hope this helps.