CODEWITHSUNDEEP
roslynvisual-studio-2015asp.net-core
rrjohnson85
rrjohnson85

Reputation: 412

Reference Issue/Missing Types

I'm periodically getting the following error on Windows 7 in Visual Studio 2015 CTP 5 with ASP.NET 5 projects:

Other core types, like Int32 & String, show the same error.

I'm using the nightly builds on MyGet and beta2 of the KRE if that matters. I have removed "aspnetcore50" from my list of frameworks, and only have "aspnet50" in my project.json.

This seems to happen for no rhyme or reason (ex. load the project in VS in the morning), and I typically have to scratch my project and recreate it to make progress. Has anyone else faced this issue? Is there anything that I can try to fix the problem? I found that unloading/reloading the project in VS works sometimes, but it usually does not help at all.

Upvotes: 2

Views: 1517

Answers (4)

rrjohnson85
rrjohnson85

Reputation: 412

I'm still not sure exactly what caused the issue, but I think that it was caused by running "kvm update" and/or using beta4 packages with a beta 2 KRE. Anyways, here is what I did to resolve the issue:

  • deleted all K runtimes at %userprofile%.kre\packages
  • deleted all Nuget packages at %userprofile%.kpm\packages
  • manually installed beta2 K runtimes
  • changed package version in project.json to beta2 ("1.0.0-beta2" or "6.0.0-beta2")
  • set the correct KRE in project settings
  • unloaded/reloaded project file

The issue has not resurfaced for me so far. If I find anything else out, I'll be sure to update this post.

Upvotes: 1

joaofilipe
joaofilipe

Reputation: 64

I had the same issue, it was caused by project dependencies ending up with 1.0.0-beta4 (because of 1.0.0-* in project.json) and I was using 1.0.0-beta2

Upvotes: 1

aidrivenpost
aidrivenpost

Reputation: 1943

Can look at this question, maybe is not the same thing but on my case I had on my project.json Microsoft.AspNet.SignalR.Server": "3.0.0-*, and when they release the beta2 version VS got the all the dependencies for SignalR witch were beta2 and this conflicted with others dependencies that were beta1.

Upvotes: 0

Kevin Pilch
Kevin Pilch

Reputation: 11615

This likely happens when you add a reference to a Portable Class Library. The project system for .csproj files will automatically add references to the Portable Facade Assemblies it detects that an added references is a PCL, but I don't believe the ASP.NET vNext project system does that.

Upvotes: 0

Related Questions