-
Notifications
You must be signed in to change notification settings - Fork 124
Cannot reference .NET Core Class Library project from ASP .NET Core Web Applicaiton project #664
Comments
TFS Bug#241383 |
@vfrank66 what version of NuGet is installed in Visual Studio (can be found in Help -> About)? |
I'm facing the same problem. Did you find how to solve it? |
Same problem here. I tried to workaround by creating a console app and converting to class library, but unfortunately that option is not available. Edit: Okay, found a workaround. Go to project.json and set emitEntryPoint to false for your console app. Hopefully it is now equivalent to a class library. |
I'm having the same issue as well. I've tried to uninstall and reinstall Visual Studio Community Update 3. I've also uninstalled .NET core 1.0.0 - VS Tooling Preview 2. Nuget package manager is v.3.5.0. Any existing core solution that I have created has this issue. Any new Core solutions also have this issue. What's interesting is that a friend of my shared a git repo that he created and I am able to reference core class libraries in that core web application. |
I get the issue to,How can I DO |
I have the same problem. Is there any way to fix it ? |
Experiencing this issue as well, any update or workarounds? |
I fixed it by installing the latest version of resharper. |
Updating resharper solved the issue for me as well, thanks @paradise!! |
@paradise i just installed the latest version of resharper, but i'm still facing the same issue.. |
I had the same issue. Uninstalling .NET and VS2015, then reinstalling did not for me. I had to do a machine reset and a clean VS2015, etc install - which then worked fine. My assumption was: windows had a bunch of earlier (prerelease) versions of ASP.NET Core & .NET Core that go tin the way |
I created a new ASP .NET Core Web Applicaiton project, then I created a .NET Core Class Library project in the same solution. From the Web project I referenced the library but I'm getting
Cannot resolve symbol
errors.It seems other people ran into this issue but for some reason it was closed (#245). I have the latest tooling as far as I can tell but the issue still seems to be happening, so I'm not sure why it was closed.
Here's my ASP .NET Core project.json file:
And here's my .NET Core class library project.json file:
The text was updated successfully, but these errors were encountered: