Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to build

See original GitHub issue

Hi folks.

I’m unable to build the repo in a fairly new PC. After getting the repo (forked - unchanged), and running the build command, I’m getting the following output:

D:\Users\Shimmy\Source\Repos\EntityFrameworkCore>build
Using KoreBuild 2.2.0-preview1-17035
D:\Users\Shimmy\Source\Repos\EntityFrameworkCore\build.ps1 : The term 'Install-Tools' is not recognized as the name of
a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
 that the path is correct and try again.
At line:1 char:126
+ ... ulture = '';& 'D:\Users\Shimmy\Source\Repos\EntityFrameworkCore\build ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Install-Tools:String) [build.ps1], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException,build.ps1

I also tried running the following in PS with the same result:

.\build /t:Compile
$env:PATH="$env:USERPROFILE/.dotnet/x64;"+$env:PATH
.\EFCore.sln

Further technical details

Operating system: Windows 10.0.16299 x64 IDE: VS 15.6.6

Issue Analytics

State:
Created 5 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

smitpatelcommented, Apr 18, 2018

corefx does not use KoreBuild. But all project in ASP.NET uses. Perhaps building asp.net universe repo could also cause it.

I would start with doing a git clean -xdf followed by build to see which version of KoreBuild it uses. Can you post output of doing build like that?

(p.s. I am online on slack. perhaps faster communication there)

0reactions

weitzhandlercommented, Apr 18, 2018

@smitpatel thanks for your help. To sum up for future reference, a specific version of KoreBuild is required. My fork was behind and had an outdated version of KoreBuild. After pulling all commits from upstream issue was fixed.