I'm using MVC 5 and .net 4.6 to create a web API that my mobile app can connect too.
Whenever I build the project I get hundreds of errors telling me that I need to add references that are already there and that literally every type in my project 'does not exist'. Some examples of these errors: (Not including the one in the title)
What I've tried:
- Added a reference to System.Runtime via nuGet. (A recommendation from this question.)
- Removed aspnetcore50 from the frameworks in the project.json file. (Another recommendation, this question.)
- Restarting VS2015, my machine.
- Going through the nuGet package manager and upgrading every package in my project to the latest.
- Actually making sure I can see the references in the references node of the solution explorer.
UPDATE: -My project.json
file looks like this. (After modifying based on Karls answer. The error list is now down to ten, however they are still the same errors as before.)
{
"commands": {
"web": "Microsoft.AspNet.Hosting --server Microsoft.AspNet.Server.WebListener --server.urls http://localhost:5000"
},
"dependencies": {
"Microsoft.AspNet.Server.IIS": "1.0.0-beta5",
"Microsoft.AspNet.Server.WebListener": "1.0.0-beta5",
"Microsoft.AspNet.Diagnostics": "1.0.0-beta5",
"Microsoft.AspNet.Mvc": "6.0.0-beta5",
"System.Runtime": "4.0.20-beta-23019"
},
"exclude": [
"wwwroot",
"node_modules",
"bower_components"
],
"frameworks": {
"dnx451": {
"frameworkAssemblies": {
"System.Data": "4.0.0.0",
"System.Data.DataSetExtensions": "4.0.0.0",
"System.Data.Linq": "4.0.0.0"
}
}
},
"publishExclude": [
"node_modules",
"bower_components",
"**.xproj",
"**.user",
"**.vspscc"
],
"version": "1.0.0-*",
"webroot": "wwwroot"
}
I'm guessing a bit here but it looks suspicious that you are using the regular System.Data.*
stuff for dnx451
but doesn't have anything to make up for it for dnxcore50
. Are you targeting the core edition as well or is it just leftovers from project creation? If you want to target the core edition and still use the old System.Data.*
stuff you'll need to wrap anything from those assemblies like this.
#if DNX451
// Do some DNX451 specific stuff here
#endif
And the other way around as well.
#if DNXCORE50
// Do some DNXCORE50 specific stuff here
#endif
But if you aren't thinking about supporting this yet I would simply remove dnxcore50
from the framework list and your errors will probably go away.
Remove bin
and obj
and rebuild.
I run dotnet restore
command on Package manager console and problem solved.
In my case, I had a project that was still set to build against a beta version of dnx. Changing it to build against the version I was using in the other projects fixed it.
This wasted lot of my time. Close the visual studio. Delete the .vs folder and restart visual studio. Everything should work fine.
For me, the problem occurred when I added a new project to my solution. I re-built the solution and the errors went away.
In my case, this is different.
First check System.Runtime reference is added to your project or not. If it is added to your project, please follow the below steps.
- Open your Reference from your project and select System.Runtime assembly.
- Right click on System.Runtime and select property.
- Change the value of SpecificVersion from False to True.
Note : In my Case I am using Visual Studio 2019 and Project Framework Version - 4.6.2
In my case, below are the steps I followed;
- I removed bin and obj and rebuild. (Didn't work)
- Unloaded the project. (It resulted in "Assets file project.assets.json not found. Run a NuGet package restore")
- I ran
dotnet restore
command via Visual Studio 2017 >> Tools >> NuGet Package Manager >> Package Manager Console.
- Rebuild solution. (Problem solved)
Took almost 2 days to fix. Tried VS Uninstall\re-install several times but did not work.
What finally worked for me...
Ran VS Installer repair.
Due to errors, I had to manually uninstall all instances MS .NET Core SDK - 2.1xxx
Ran VS Installer repair.
No errors.
Remove bin and obj and rebuild.
Ran dotnet restore
command on Package manager console and problem solved.
I just opened Visual Studio "As Administrator" and it worked!