I come across these issues pretty frequently and the pattern is constant enough that I reckon it deserves just a little bit of effort to jot down some practices to streamline things.
The concepts are pretty broad and generally interchangeable across technologies but I’m picking .
Today it only works on the prerelease tag, but in the next version of Nu Get it'll work on more parts of the version. This also shows up in Visual Studio under the references node: The nodes marked as yellow are unresolved.
I had to open up one of the files in the "wrap" folder for the "adminui.wqlqueryengine.dll" that had a "dependencies" section as well and remove it from there and then everything started to build and restore without any problems. Also what is relative folder structure of your solution root comparing to a project reference you are trying to add?I was able to reproduce the issue in a new MVC6 solution created with the beta8 tools; I created a solution with a new MVC6 project and then added a class library (non-packaged) to the solution. It seems that if the files for the external references in wrap folder have a reference to the 'dnx451' framework than it seems this bug appears. I add an non-packaged library project to the solution and then adding it as a project reference in a web app does not cause this problem. NET and Web Tools 2015 (RC1 Update 1) 14.1.11120.0 Created a ASP.I then removed the reference to core CLR from and switched the class library to build against . I then added the new class library to the via right-click 'Add - Reference', restored packages, and confirmed that the class library appears in the solution explorer. So the simple way to get Visual Studio 2015 to 'see' the external . It only occurs for existing projects that were not created in my solution. NET Web Api project and added a second Class Library project using . In the Class Library project I am trying to add a reference to 3 dlls to make SCCM SDK calls: adminui.wqlqueryengine microsoft.configurationmanager.managedbase microsoft.configurationmanagement.managementprovider The first two DLLs are loaded without any issues however the last one ending with "managementprovider" is giving me the following error: "NU101 Dependency microsoft.configurationmanagement.managementprovider I was able to solve the issue but I think that there is a bug somewhere here.I looked at this post and other posts related to the error on Stackoverflow and elsewhere, and tried all suggestions that I found.The insanity peaked when I reinstalled Visual Studio 2008, rebooted and saw the error reappear. The next day I realized the publish error was actually being caused by directory permissions. Here's what I've learned from my day of hell: Are you working with some king of unmanaged, platform-specific code?There are few things more frustrating than trying to make other peoples’ code work; broken references, missing dependencies, extraneous and useless files – it’s all part of the joy of sharing the project love around.