-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
OK... After resolving the issue regarding spaces in the path that was causing dotnet-cli to crash immediately on launch, I now ran into another issue. When I run dotnet restore, it fails to resolve any of the NuGet packages specified in my project.json. Here's the console output when I try:
info : Running restore with 16 concurrent jobs.
info : Restoring packages for C:\Users\William\Documents\GitHub\ChocolateyApps\Core\Wix.Core\project.json...
error: Unable to resolve Microsoft.CSharp (>= 4.0.0) for .NETPlatform,Version=v5.4.
error: Unable to resolve Microsoft.Win32.Primitives (>= 4.0.0) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Collections (>= 4.0.10) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Collections.NonGeneric (>= 4.0.0) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.IO (>= 4.0.10) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.IO.FileSystem (>= 4.0.0) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Linq (>= 4.0.0) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Reflection (>= 4.0.10) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Reflection.TypeExtensions (>= 4.0.0) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Runtime.InteropServices (>= 4.0.20) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Threading (>= 4.0.10) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Threading.Thread (>= 4.0.0) for .NETPlatform,Version=v5.4.
error: Unable to resolve System.Xml.ReaderWriter (>= 4.0.11) for .NETPlatform,Version=v5.4.
info : Committing restore...
info : Restore failed in 398ms.
Can anyone help me? @wtgodbe is waiting for my input to triage coreclr#2143, and I cannot provide him any feedback due to this issue. He has asked twice now, and I do not want to keep him waiting much longer.
(On an aside: Not to be mean, but whose idea was this large, breaking change, anyway? .NET CLI used to just work for me, but now I cannot even restore packages successfully. This is really annoying because I cannot continue working on my .NET Core app until these issues are resolved!)