Open ManuelDeLeon opened 8 years ago
Expected coreclr library not found in package graph. Please try running dotnet restore again.
This mentions dotnet restore
, and in the error list we see a lot of warnings mentioning deprecated options. Did you install the recent .NET Core RC2 tooling?
The newest tooling (for RC2) uses RC2 by default. But this project is based on RC1. In order for the tooling to use RC1 you need to have a global.json present, which does not exist in this project.
Check out this: https://blogs.msdn.microsoft.com/visualstudio/2016/05/16/announcing-updated-web-development-tools-for-asp-net-core-rc2/ Specifically the section "Support for RC1 and RC2 projects".
To work around the bower error, you can run bower install --force
.
When a Visual Studio project includes bower folders, it creates empty folders before running bower install
which causes this error. (I actually came across this GitHub issue by searching for a better solution that doesn't require the developer to use --force
, which I haven't found yet 😿 )
What worked for me was I deleted bootstrap and jQuery folders in my wwwroot folder, and then in my Bower folder right click each one and select "Restore package". Using VS2017.
I can get it working from the command line (
npm start
) but when I open the project with Visual Studio I'm in a world of hurt.Out the bat it tries to update the dependencies but fails:
If I try to build the project I get:
At this point I figure I'm missing a typed file so I add
tsd install es6-shim
(jasmine too for good measure). I try to build the project and now I get:Key point as I see it:
Expected coreclr library not found in package graph. Please try running dotnet restore again.
At this point I don't know what to do because I'm pretty sure I shouldn't run dotnet restore... but I do it anyway and the project now breaks even in the console.
/help