build.cmd won't run on Windows with only .NET Core installed

[moodmosaic]

Downloading NuGet.exe ...
Feeds used:
  C:\Users\Nikos\.nuget\packages\
  https://api.nuget.org/v3/index.json

Attempting to gather dependency information for package 'FAKE.Core.4.63.2' with respect to project 'build\tools', targeting 'Any,Version=v0.0'
Gathering dependency information took 1.65 sec
Attempting to resolve dependencies for package 'FAKE.Core.4.63.2' with DependencyBehavior 'Lowest'
Resolving dependency information took 0 ms
Resolving actions to install package 'FAKE.Core.4.63.2'
Resolved actions to install package 'FAKE.Core.4.63.2'
Retrieving package 'FAKE.Core 4.63.2' from 'C:\Users\Nikos\.nuget\packages\'.
Adding package 'FAKE.Core.4.63.2' to folder 'C:\Snapshot\Fare\build\tools'
Added package 'FAKE.Core.4.63.2' to folder 'C:\Snapshot\Fare\build\tools'
Successfully installed 'FAKE.Core 4.63.2' to build\tools
Executing nuget actions took 436.42 ms
Running FAKE Build...
C:\Program Files\Git\mingw64\bin\git.exe describe --tags --long --abbrev=40 --first-parent --match=v*
v2.1.1-1-g71eaf12a6553a6ddd84a0fc52e78f19ada766d0a
Building project with version: LocalBuild
Shortened DependencyGraph for Target CompleteBuild:
<== CompleteBuild
   <== NuGetPack
      <== CleanNuGetPackages
      <== Test
         <== Build
            <== Verify
               <== RestoreNuGetPackages
               <== VerifyOnly
            <== BuildOnly
         <== TestOnly

The running order is:
  - CleanNuGetPackages
  - RestoreNuGetPackages
  - VerifyOnly
  - Verify
  - BuildOnly
  - Build
  - TestOnly
  - Test
  - NuGetPack
  - CompleteBuild
Running build with 1 worker
Starting Target: CleanNuGetPackages
Creating C:\Snapshot\Fare\build\NuGetPackages
Finished Target: CleanNuGetPackages
Starting Target: RestoreNuGetPackages
Building project: Src/Fare.sln
  c:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe  Src/Fare.sln /t:Restore /m  /nodeReuse:False  /v:m  /p:RestorePackages="False" /p:AssemblyVersion="2.1.0.0" /p:FileVersion="2.1.1.0" /p:InformationalVersion="2.1.1.1-71eaf12a6553a6ddd84a0fc52e78f19ada766d0a" /p:PackageVersion="2.1.1.1" /logger:Fake.MsBuildLogger+ErrorLogger,"C:\Snapshot\Fare\build\tools\FAKE.Core\tools\FakeLib.dll"
Microsoft (R) Build Engine version 4.7.3056.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

C:\Snapshot\Fare\Src\Fare.sln.metaproj : error MSB4057: The target "Restore" does not exist in the project. [C:\Snapshot\Fare\Src\Fare.sln]
Running build failed.
Error:
Building Src/Fare.sln failed with exitcode 1.

---------------------------------------------------------------------
Build Time Report
---------------------------------------------------------------------
Target                 Duration
------                 --------
CleanNuGetPackages     00:00:00.0025071
RestoreNuGetPackages   Failure
Total:                 00:00:01.0394329
---------------------------------------------------------------------
Status:                Failure
---------------------------------------------------------------------
---------------------------------------------------------------------
  1) Building Src/Fare.sln failed with exitcode 1.
  2) MSB4057: C:\Snapshot\Fare\Src\Fare.sln.metaproj(0,0): The target "Restore" does not exist in the project.
---------------------------------------------------------------------

30, #31, /cc @zvirja

[moodmosaic]

>dotnet --version
2.1.300

[zvirja]

@moodmosaic Yes, it seems that the root cause is the missing VS installation. We could rewrite scripts to use dotnet only, so it will work with dotnet SDK only.

[JimiC]

Your problem lies in the attempt to "Restore" the NuGet packages, not with missing VS installation. Resolve that and you will be fine with just MSBuild.exe installed.

[moodmosaic]

It is some MSBuild task that’s failing, yes. Most likely the Restore one, as shown from that error.

I’m putting this issue as a note so we can come back and fix it. Right now it is a blocker one.