VS2015 unable to resolve references to class library in solution

[austinlparker]

Since updating to beta 8, VS2015 is unable to resolve references to my class libraries. The libraries are wrapped, and the solution builds and runs correctly - I am unable to use intellisense or autocomplete, however. 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. I then removed the reference to core CLR from project.json and switched the class library to build against .NET 4.5.1. I then added the new class library to the project.json via right-click 'Add - Reference', restored packages, and confirmed that the class library appears in the solution explorer. After this, I attempted to reference the new class library via a using statement, and VS shows an error claiming that the type or namespace does not exist. I am able to build the solution, however.

[felipem]

I've had this exact same issue. Externally referenced .NET 4.5 projects are not recognized in VS2015. The project (ASP.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.

Any solutions to this? I've tried clearing the dnx package cache, re-getting source from source control into a new path.

Thanks,

[sayedihashimi]

So this is a regression from previous releases?

[felipem]

Perhaps? 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.
In Beta8 it worked perfectly for a few weeks until I applied a workaround to publish as mentioned on asp.net issue dotnet/aspnetcore#1017

[felipem]

Found a temporary workaround until this bug is fixed.

It seems that if the project.json files for the external references in wrap folder have a reference to the 'dnx451' framework than it seems this bug appears. So the simple way to get Visual Studio 2015 to 'see' the external .NET libraries again are as follows:

1. Close or unload the project in question
2. Go into each project.json file in the wrap folder and replace framework dnx451 with net45 (or remove dnx451 if you have both frameworks referenced).
3. Reload the project
4. Now you can re-add the dnx451 framework reference in the project.json files again. This is needed to get around the publish bug mentioned previously (Can't publish asp.net 5 application after update to beta8 - the dependency … could not be resolved dotnet/aspnetcore#1017).

Obviously a sucky workaround for two bugs. Hopefully fixed soon!

[sayedihashimi]

Sorry for the delay here. Is this still an issue?

[miloush]

VS 14.0.24720.00, ASP.NET tools 14.1.11120.0. (Update 1)

1. Create a new ASP.NET Web Application (framework version left to default 4.5.2)
2. Select Empty Web ASP.NET 5 Template
   (ignore the JavaScriptWebExtensionsPackage package load failure I guess)
3. Right click on Solution and Add New Project.
4. Select Visual C# > Class Library (framework version left to default 4.5.2)
5. Edit project.json /frameworks to have only net452 (note there is no intellisense for these values :()
6. Save the file which creates bunch of errors and turns references section into warning.
7. Right click on the web project and do Restore Packages (this should not be necessary for me).
8. Right click on the web project and Add Reference.
9. From Solution, select the class library project just created.
10. You get NU1001 The dependency ClassLibrary1 >= 1.0.0-* could not be resolved (this should not happen either).
11. Okay, maybe it needs building, build the solution. Nothing changes.
12. Restore packages and builds solution again (this should not be necessary for me)
13. You get MSB3274 warning The primary reference ... could not be resolved because it is against the 4.5.2 framework. This is a higher version than the currently targeted 4.5.1.
14. Note that 4.5.1 version was nowhere mentioned or selected. And does not seem you can change it. Also probably relevant to DNX4.5.1 selected as framework even if I select 4.6 inside VS when creating project (RC1) #326.
15. Well go ahead and change the new library project to target 4.5.1. Note you might be not able to do this with existing libraries.
16. Save the project and build the solution. Success!
17. Go to Startup.cs and wherever, e.g. in ConfigureServices, type Class1.
18. Not resolved. Try fully qualified name: ClassLibrary1.Class1 c;
19. CS0246 This type or namespace 'ClassLirbary1' could not be found.
20. Build the solution again, output window says success.
21. Hit F5 to check if it really works. Browser opens but never loads the web site, any breakpoints created in the code remain unresolved.

This still looks like an issue to me, and really non-trivial amount of work needed to add a class library to a web site!

[sayedihashimi]

TFS: 174588
I've added this to our internal TFS, we will reply back here soon.

[sljohnst]

Chiming in here with what seems like it might be another variation of this problem...

I'm running VS 14.0.24720.00 Update 1, ASP.NET and Web Tools 2015 (RC1 Update 1) 14.1.11120.0.

I create a new solution containing an ASP.NET web application with .NET Framework 4.5.1. I add an existing class library project (non-packaged) to the solution. If I add a project reference in the web app to the class library, I get the NU1001 "The dependency ChartCapture.Common >= 1.0.0-* could not be resolved" error, and I cannot build.

Adding a project reference in this scenario will create a “wrap” folder at the project level, which isn’t working.

Adding a new non-packaged library project to the solution and then adding it as a project reference in a web app does not cause this problem. It only occurs for existing projects that were not created in my solution.

Workaround:

1. Build the class library project.

2. In the web application, add an assembly reference to the class library DLL. This will create a “wrap” directory at the same level as the solution file, and it contains a project.json file for the class library.

3. I can convert the assembly reference to a project reference by editing the project.json file, adding the wrappedProject entry.

4. To see the resulting change in the reference in the IDE, close the solution and reopen it.

Here is example of a project.json file (at the solution level) BEFORE I have edited it:
{
"version": "1.0.0-*",
"frameworks": {
"dnx451": {
"bin": {
"assembly": "../../src/Common/obj/Debug/Common.dll",
"pdb": "../../src/Common/obj/Debug/Common.pdb"
}
}
}
}

and AFTER I have changed it to a project reference:
{
"version": "1.0.0-*",
"frameworks": {
"dnx451": {
"wrappedProject": "../../src/Common/Common.csproj",
"bin": {
"assembly": "../../src/Common/obj/{configuration}/Common.dll",
"pdb": "../../src/Common/obj/{configuration}/Common.pdb"
}
}
}
}

[sljohnst]

Update...

1. I cannot make the project.json entry configuration-neutral by replacing 'Debug' with '{configuration}', like I did in my previous post. If I do, I get build errors when I write code using the class library, because classes in the class library cannot be found.
2. Even though I can convert the assembly reference to a project reference (by manually modifying the project.json for the class library, adding a wrappedProject, as I mentioned above), and the projects will successfully build, this messes up Intellisense.

So, for now, it's probably best for me to just use an assembly reference to the class library's Debug DLL.

[ilyalozovyy]

I think I am having a related issue.
Running VS 14.0.24720.00 Update 1, ASP.NET and Web Tools 2015 (RC1 Update 1) 14.1.11120.0

Created a ASP.NET WebApi project and added a second Class Library project using .NET 4.5.
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 >= 1.0.0-* could not be resolved"

I've tried the recommendations listed above without any luck.

[ilyalozovyy]

I was able to solve the issue but I think that there is a bug somewhere here.
I noticed when I removed the assembly that was causing the problem from the "dependencies" section in the project.json and performed a build or executed "dnu restore" command that the issue still occurred.
I had to open up one of the project.json 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.

[abpiskunov]

@sljohnst Can I see your global.json?

Also what is relative folder structure of your solution root comparing to a project reference you are trying to add? (I assume you used Add Reference dialog to add a project reference?)

[javivalero]

Really a big problem, if we can't add references to class libraries. A work around could be add as nuget package, but we loose the capability to debug.

I a m working in a project and we have decided start with the ASP.net core and MVC6, so a work around will be appreciated.