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.

CLI attempts NuGet Restore instead of using provided DLL path

See original GitHub issue


I have not published my tooling project to NuGet yet. I plan to today, but I have a curious message, error, or warning, that is happening at the moment.

I uniquely renamed my project output such that it no longer conflicts with existing NuGet packages. I am finding this kind of error during the build. I think that the local path is being used, but the error in the meantime is curious. I’m not sure there is anything else I can do with that from my end, when the build resolves, the asset is there, so to speak.

Error / NU1101 / Unable to find package dotnet-mytool. No packages exist with this id in source(s): ... / MyTool.Integration.Tests / path\to\MyTool.Integration.Tests\MyTool.Integration.Tests.csproj

That being said on the one hand, I’m not sure my targets do not need a bit of fine tuning. There is one in particular depending on some curious Microsoft Build targets, which are triggered at odd times when the asset might not be there, i.e. preparatory phases when the build outputs might not otherwise be there, for instance.

So, really, I’m just curious, if we provide a full path to the DLL assets, isn’t that sufficient to preclude this sort of condition? The default position, then, would be to ask for a NuGet Restore, for example.

Environment data



Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:18 (6 by maintainers)

github_iconTop GitHub Comments

mwpowellhtxcommented, Jul 3, 2019

@peterhuene May have just identified an actual typo in my dependencies.

peterhuenecommented, Jul 2, 2019

Try using dotnet exec <path_to_dll> .... This command will only execute the target assembly and will not invoke the .NET Core SDK at all (and thus the fallback logic in the SDK). If the assembly is not found, the command will immediately fail.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting NuGet Package Restore in Visual Studio
This error occurs when you attempt to build a project that contains references to one or more NuGet packages, but those packages are...
Read more >
NuGet Package Restore Not Working
Open solution, go into Tools > Nuget Package Manager > Package Manager Settings and Clear all Nuget caches . Check the console because...
Read more >
How to Use NuGet Packages: The Ultimate Guide
To restore the solution with the help of the NuGet CLI, use the restore command. It will restore all the packages available in...
Read more >
Dotnet restore vs nuget restore. Share. In my code repo, there
I am trying to restore NuGet packages in my project using the CLI. Otherwise continue to the sections that follow. nuget restore works...
Read more >
Nuget restore - system cannot find file - Microsoft.Build. ...
Everytime I try to run Nuget restore I get this error. I get on another server that I am trying to put a...
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 Post

No results found

github_iconTop Related Hashnode Post

No results found