'The type 'Expression<>' is defined in an assembly that is not referenced

In ASP.NET MVC 4.5.2 Framework, after typing @Html.LabelFor() or @Html.EditorFor() in a view, I'm getting this error:

The type 'Expression<>' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

I have added assembly reference System.Core.dll, Version 4.0.0.0, Runtime Version v4.0.30319, and also I did in web.config.

asp.net-mvc asp.net-mvc-5.1

Solution 1:^[1]

I have run in the same issue as you, albeit much later. The issue was that I was not able to access Razor views (.cshtml) as I was getting an error stating that I had a missing assembly reference, namely System.Web.Mvc, even though it was in the project references. After investigation, I have noticed that the installed NuGet version was 5.2.3, while the project required 5.2.0. The solution is to downgrade the MVC version.

Go to Project-> NuGet Package Manager.
Search for MVC; it's going to be the first result.
Next is to select downgrade from the drop-down in the details of the NuGet package and submit.

Confirm all the dialogs and you are ready to go.

Solution 2:^[2]

I am not sure if you are still having this issue or not but i was having the same issue as well.

I was able to find the solutions here

https://stackoverflow.com/questions/6496223/compilation-error-in-net-4-0-web-config-linq-not-found

<add assembly="System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

<add assembly="System.Data.DataSetExtensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

<add assembly="System.Xml.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

I hope this helps..

Solution 3:^[3]

This error means that Visual Studio is unable to locate the System.Web.Mvc assembly to power its intellisense for Razor views. One or both of the following may be required to fix it.

Ensure the version of the .NET framework for the compilation property in the main web.config (the one in the website root) is the same as that specified in the project properties.

[root]/Web.config:

<system.web>
    <compilation targetFramework="4.6" />

Project Properties:

Ensure the version of the MVC assembly specified in the views web.config (the one in the views folder) is the same as the MVC assembly you are using in your project.

[views folder]/web.config:

<system.web.webPages.razor>
    <host factoryType="System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

MVC Assembly Reference Properties:

Solution 4:^[4]

Close the cshtml file
Rebuild solution
Open cshtml file
Still errors? Restart Visual studio
Still errors? Use ctm1988's answer

Solution 5:^[5]

I have tried most of these, what eventually worked for me was unloading the project, edit the csproj file, and add the following:

<Reference Include="System.Core" />

https://stackoverflow.com/a/38371981/2335660

Solution 6:^[6]

Deleting [projectName].csproj.user file from the project directory helped for me.

Solution 7:^[7]

I just had the same exact issue and none of the solutions fixed the problem. I had to add this into my web.config within System.Web

<compilation debug="true" targetFramework="4.5" />
<httpRuntime targetFramework="4.5" />

I had removed it when changing some of the config around.

Solution 8:^[8]

I've had the same problem with missing assembly and it happened that VS2017 build has not copied it properly into the Bin folder. These steps helped me:

Navigate to the web project's References node

Find the reference to System.Core

Open the VS Properties Window

In the properties window, change Copy Local: False to True

from this comment: CS0012: The type '#####Any type#####' is defined in an assembly that is not referenced

Solution 9:^[9]

In my case this message was shown only when Resharper was turned on. I have cleared Resharper cache, restarted VS, turned Resharper off and turned it on again. The message has dissapeared.

Solution 10:^[10]

I did ALL of the above and in the end found that what solves it for me (on a .net framework 4.7.1 site with MVC 5.2.4) was adding this into the root web.config within <compilation> -

<assemblies>
  <add assembly="System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
</assemblies>

Solution 11:^[11]

In Web.config I needed to change:

  <system.web>
    <compilation debug="true" targetFramework="4.7">

  <system.web>
    <httpRuntime targetFramework="4.7" />
    <compilation debug="true" targetFramework="4.7">

Solution 12:^[12]

Check that the cshtml file Build Action is set to 'Content'.

I use ReSharper and have noticed that for some reason the file that is generated defaults to 'None' when invoking the template.

Solution 13:^[13]

Add the following to Web.config (in root). I tried absolutely everything of earlier suggestions and nothing worked until I found the below. Hope it will save time for someone else.

I use targetFramework="4.6.1", but change it to the version you use if different.

<system.web>
   <compilation debug="true" targetFramework="4.6.1" />
   <httpRuntime targetFramework="4.6.1" />
</system.web>

Solution 14:^[14]

Add the System.Core.dll file to the bin folder manually. Restart VS and build project. Solved for me

Had design errors in all views on @Html helpers and on my Kendo grids.

Adding System.Core assembly in Web.config did nothing, nor did downgrading the MVC version. And error when trying to add reference to System.Core manually:

A reference to 'System.Core' could not be added. This component is already automatically referenced by the build system.

Make sure to check that TargetFramework in project properties matches the one in project web.config.

Screenshot of bin folder

Solution 15:^[15]

Well, I got it fixed by correcting the assembly reference in /Views/web.config, see the image:

Solution 16:^[16]

delete bin, .vs and obj directory. after build your project on the visual studio.

Solution 17:^[17]

Restarting Visual studio worked for me.

Solution 18:^[18]

For me, there was an option under the project menu to "Enable C# 6.0/VB 14". Selecting this option did the trick. Previously I tried modifying the web.config, restarting Visual Studio, etc as was suggested in this post.

Solution 19:^[19]

I faced the same problem. Basically the problem is using different version of System.Web.Mvc. So the best thing you should the open Tools > Nuget Package Manager > Manage Nuget Packages for Solution. You can probably see System.Web.Mvc on the Cosolidate tab. Upgrade or downgrade would be the best option. If you use the latest .Net framework, which is currently .Net 4.6.1, you should upgrade the all System.Web.Mvc versions to 5.2.4.0. Good luck!

Solution 20:^[20]

This happened with one of my views - all the others were fine. I did the following:

Create a new view
Copy and paste the contents from the old view to the new one
Deleted the old one
Renamed the new one to the old one

Solution 21:^[21]

Close the file
Clean the solution
Build the solution
Reopen the file

Solution 22:^[22]

Try to add

using system.Linq.Expressions;

Solution 23:^[23]

I had this problem too. Changing targetFramework="4.5.2" to targetFramwork="4.5" in web.config file solved it.

Solution 24:^[24]

If you get this in only one or two CSHTML files... it's a corrupt file.

I've had this happen with a corrupt file that has some hidden unicode characters. Try copying all the text of the document to a fresh notepad instance. Clear the contents of the original file and save... if the file length is > 0, there's something awry.

Delete the file and save your notepad instance over the old version. All the errors went away for me.

I've had this happen a couple of times in my solution. Not sure what's causing it, but I suspect it's Resharper screwing up when it starts to swallow huge chunks of memory into the abyss.

Am I the only one who has a love / hate relationship with Resharper?

Solution 25:^[25]

This can be caused if you have multiple projects in your solution that don't all target the same version of the .NET Framework. For example, if your web app project targets .NET 4.5 and you have an assembly reference to another project in the solution that targets .NET 4.5.2. To fix this you need to change your projects to all target the same version of the .NET Framework.

Solution 26:^[26]

If none of the answers work use this one. I faced the same issue! Actually configuration.cs file in migrations folder was missing/deleted. I did delete migrations folder and also did delete migrations table from database. Next in Package Manager Console (PM) used following commands:

Enable-Migrations -Force
Add-Migration Initial
update-database

This process recreated the configuration.cs file and everything worked perfectly!

Solution 27:^[27]

Check your project properties to get the Target framework. I resolved this issue in my project by matching for my target framework .NET framework 4.6.1 MVC 5.2.3 was the apt solution. I got that MVC version from NuGet.

Solution 28:^[28]

In my case the solution was to move the ConnectionString inside the Web.Config. This statement should be after AppSettings section.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	honk
Solution 2	Community
Solution 3	Tom Bowers
Solution 4	CularBytes
Solution 5	Community
Solution 6	Robo Burned
Solution 7	BurnsBA
Solution 8
Solution 9	Neshta
Solution 10	Andy
Solution 11	juFo
Solution 12	Kevin R.
Solution 13	Njål Eide
Solution 14
Solution 15	×¡×˜× ×œ×™ ×’×¨×•× ×Ÿ
Solution 16	Nisanur
Solution 17	Mangesh Kadam
Solution 18	Aggromonster
Solution 19	Mehmet Taha Meral
Solution 20	Liam
Solution 21	Jeph
Solution 22	user1223339
Solution 23	Owen Pauling
Solution 24	user910531
Solution 25	Chris Pietschmann
Solution 26	Shah Aadil
Solution 27	Sukesh Mullassery
Solution 28

'The type 'Expression<>' is defined in an assembly that is not referenced

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]

Solution 12:[12]

Solution 13:[13]

Solution 14:[14]

Solution 15:[15]

Solution 16:[16]

Solution 17:[17]

Solution 18:[18]

Solution 19:[19]

Solution 20:[20]

Solution 21:[21]

Solution 22:[22]

Solution 23:[23]

Solution 24:[24]

Solution 25:[25]

Solution 26:[26]

Solution 27:[27]

Solution 28:[28]