question-mark
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.

NU1001 The dependency Microsoft.NETCore.App >= 1.0.1 could not be resolved.

See original GitHub issue

Steps to reproduce

VS 14.0.25431.01 Update3 .NET Core 1.0.1 - VS 2015 Tooling Preview 2 downloaded from this link

create a dotnetcore console app (here is the project.json)

{
  "version": "1.0.0-*",
  "buildOptions": {
    "emitEntryPoint": true
  },

  "dependencies": {
    "Microsoft.NETCore.App": {
      "type": "platform",
      "version": "1.0.1"
    }
  },

  "frameworks": {
    "netcoreapp1.0": {
      "imports": "dnxcore50"
    }
  }
}

Expected behavior

Everything is created by VS by default…I should be able to start developping…I don’t understand how could it fail on package restore

Actual behavior

C:\Program Files\dotnet\dotnet.exe restore "c:\users\watashiSHUN\documents\visual studio 2015\Projects\ConsoleApp1\.vs\restore.dg"
MSBUILD : error MSB4025: The project file could not be loaded. Data at the root level is invalid. Line 1, position 1. [c:\users\watashiSHUN\documents\visual studio 2015\Projects\ConsoleApp1\.vs\restore.dg]

under properties->references->.netcoreapp,version=v1.0->microsoft.netcore.app->NU1001 The dependency Microsoft.NETCore.App >= 1.0.1 could not be resolved.

Environment data

dotnet --info output:

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:8 (1 by maintainers)

github_iconTop GitHub Comments

6reactions
ghostcommented, Dec 1, 2016

Rather then sending people through a wormhole of issues and wiki markdown documents could you please re-open this issue and advise on the fix status?

Also rather than imposing laborious repro’s as a burden on your consumers would it be too harsh to ask you guys to find and fix the problem?

After all you are the originators here and should probably take responsibility for finding and fixing the problems.

The community is telling you it does not work.

2reactions
ghostcommented, Dec 1, 2016

To quote your markdown “To migrate a project open a command prompt and go to the project’s root directory. From here, type dotnet migrate and let the tool do its work. For most projects, that’s it!”

Nah dude … it does not.

C:\code\amazon-micrososervices\lambda-has-gots-core>dotnet migrate

Unhandled Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path ‘C:\Users\Gavin.nuget\packages.tools\Amazon.Lambda.Tools’. at System.IO.Win32FileSystemEnumerableIterator1.HandleError(Int32 errorCode, String path) at System.IO.Win32FileSystemEnumerableIterator1.CommonInit() at System.IO.Win32FileSystemEnumerableIterator1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler1 resultHandler) at System.IO.Win32FileSystemEnumerableFactory.CreateFileNameIterator(String path, String originalUserPath, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption) at System.IO.Win32FileSystem.EnumeratePaths(String fullPath, String searchPattern, SearchOption searchOption, SearchTarget searchTarget) at System.IO.Directory.EnumerateFileSystemNames(String path, String searchPattern, SearchOption searchOption, Boolean includeFiles, Boolean includeDirs) at System.IO.Directory.EnumerateDirectories(String path) at Microsoft.DotNet.Cli.Utils.ToolPathCalculator.GetAvailableToolVersions(String packageId) at Microsoft.DotNet.Cli.Utils.ToolPathCalculator.GetBestLockFilePath(String packageId, VersionRange versionRange, NuGetFramework framework) at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.GetToolLockFilePath(LibraryRange toolLibrary, String nugetPackagesRoot) at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.GetToolLockFile(LibraryRange toolLibrary, String nugetPackagesRoot) at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.ResolveCommandSpecFromToolLibrary(LibraryRange toolLibraryRange, String commandName, IEnumerable1 args, ProjectContext projectContext) at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.ResolveCommandSpecFromAllToolLibraries(IEnumerable1 toolsLibraries, String commandName, IEnumerable1 args, ProjectContext projectContext) at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.ResolveFromProjectTools(String commandName, IEnumerable1 args, String projectDirectory) at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.Resolve(CommandResolverArguments commandResolverArguments) at Microsoft.DotNet.Cli.Utils.CompositeCommandResolver.Resolve(CommandResolverArguments commandResolverArguments) at Microsoft.DotNet.Cli.Utils.CommandResolver.TryResolveCommandSpec(String commandName, IEnumerable1 args, NuGetFramework framework, String configuration, String outputPath) at Microsoft.DotNet.Cli.Utils.Command.Create(String commandName, IEnumerable1 args, NuGetFramework framework, String configuration, String outputPath) at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry telemetryClient) at Microsoft.DotNet.Cli.Program.Main(String[] args)

Read more comments on GitHub >

github_iconTop Results From Across the Web

error NU1001: The dependency Microsoft.NETCore.App >= ...
dotnet --info output: project.json(3,30): error NU1001: The dependency Microsoft.NETCore.App >= 1.0.1 could not be resolved.
Read more >
NU1001 The dependency Microsoft...>=1.0.0 could not be ...
Today i open my App in Visual Studio 2015 but there was an ERROR by the References about: NU1001 The dependency Microsoft.ApplicationInsights.
Read more >
NuGet Error NU1100
A dependency could not be resolved. This is a generic issue for types that are not packages or projects. Solution 1. Open the...
Read more >
Debugging into ASP.NET Core Source - Code with Steve
Sources 1.0.0. The exact error in my case was NU1001 The dependency Microsoft.Extensions.PropertyHelper.Sources >= 1.0.0-* could not be resolved ...
Read more >
Troubleshoot .NET Framework targeting errors
To resolve the error, make sure that your application targets a .NET version that's compatible with the version that's targeted by the projects ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found