(I assume you used Add Reference dialog to add a project reference?) Really a big problem, if we can't add references to class libraries.To avoid these errors, it is better in these cases to add project-to-project references.
If your application attempts to use a broken reference, an exception error is generated.
The inability to find the referenced component is the primary trigger for the error, but there are several situations in which a reference can be considered broken.
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.
Since updating to beta 8, VS2015 is unable to resolve references to my class libraries. NET MVC Web API 6 project) builds and publishes just fine but VS2015 visually marks any references to the external library as errors and intellisense doesn't recognize objects in the libraries. I've tried clearing the dnx package cache, re-getting source from source control into a new path. I couldn't get external references working in beta7 due to issues mentioned on issue #120 so can't really say if this issue existed before.
The libraries are wrapped, and the solution builds and runs correctly - I am unable to use intellisense or autocomplete, however. In Beta8 it worked perfectly for a few weeks until I applied a workaround to publish as mentioned on issue aspnet/Home#1017 Found a temporary workaround until this bug is fixed.
[today] This morning, after going through a few more iterations, I think I know what my problem was.
I need to do a VIsual Studio REBUILD, not just BUILD.
I have a helper project which I use in all the applications that I create.
It contains some extension methods and a bunch of generic helper classes, controls etc.
Everytime I do a make changes, do a rebuild (not just build), and then copy over the dll, the changes show up correctly on the IIS6 box.