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

Question

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.

Possible duplicate of [VS 2015 IntelliSense: Assembly Not Referenced Error](https://stackoverflow.com/questions/31599087/vs-2015-intellisense-assembly-not-referenced-error) — Owen Pauling, Jul 01 '19 at 08:32

score 66 · Answer 1 · edited May 23 '17 at 12:26

66

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..

edited May 23 '17 at 12:26

Community

1
1

answered Aug 03 '15 at 13:59

ctm1988

681
1
4
6

already i said that.. i have try this one before i posting this question. any way thanks both of you – mansoor Dec 28 '15 at 05:02
3

fine! It works. Note that you should close and reopen cshtml file to take effect. – Mahdi Ataollahi Apr 30 '19 at 11:25
This worked for me once I went through all the web.configs and made sure the versions matched as in https://stackoverflow.com/a/37381294/8684119 – AMG Feb 03 '20 at 15:39
It works, but i found this solution a little bit dirty. Anyway, in my case i add only the reference to System.Core – T-moty May 19 '20 at 14:21
1

This solution isn't "dirty". It's literally exactly what the error tells you to do. What I didn't understand was that it needed to go into the web.config file. – Ricky Feb 12 '21 at 21:48

score 52 · Answer 2 · answered May 23 '16 at 01:07

52

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:

answered May 23 '16 at 01:07

Tom Bowers

4,951
3
30
43

4

This Worked for me. Many Thanks. – vibs2006 Apr 12 '17 at 11:25
1

This resolved it for me too, but not directly. I had to delete the file with wrong version from my bin folder, update mvc via nuget, and then it placed the correct version in my bin folder and it worked. if you still keep getting the wrong version in the bin folder after updating via nuget, delete the existing one in the bin folder – Joshua K Sep 28 '18 at 14:53
Thank you. I updated Microsoft.AspNet.Mvc through NuGet to v5.2.7 and began to see this error in .schtml file, while app was still working. It turned out web.config in Views folder under it was still v5.2.3. Modifying it to v5.2.7 helped. – vkelman Jan 08 '20 at 13:54
This worked - thank you! Remembering to check the [Views]/web.config was key for me. Version matched everywhere else but there! – Jay Dawkins Feb 15 '20 at 17:32
grateful , in my case mvc version and mvc assembly version was different. i change the all 5.0.0.0 version to 5.2.3.0 in view/Web.config file. – hossein andarkhora Jun 07 '23 at 07:09

score 45 · Accepted Answer · edited Mar 17 '16 at 20:22

45

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.

edited Mar 17 '16 at 20:22

honk

9,137
11
75
83

answered Jan 06 '16 at 21:54

Prashant2008

508
5
3

17

How did you notice your project required 5.2.0? – Vanice Sep 13 '16 at 07:09
3

@Vanice I think it depends on .NET Framework version: .NET 4.5.2 -> MVC 4.0.0; .NET 4.6.0 -> MVC 5.2.0; .NET 4.6.1 -> MVC 5.2.3. (Not confirmed) – JoaoRibeiro Jan 16 '17 at 09:24
11

I'm using .net 4.7 and still have this annoying error – Sven Jan 10 '18 at 13:24
2

I had the same issue, turns out it was my debug value in the web.config was set to false. Set it to "True" – mlaribi Dec 17 '18 at 16:36
I have tried the above solution its working well. My VS Solution Version was of 4.6.2 and I downgraded the MVC to 5.2.3 from 5.2.4 .So I came to know that MVC 5.2.3 is compatible with .Net 4.6.2 – Ibrahim Inam Sep 03 '19 at 08:07

score 27 · Answer 4 · answered Dec 26 '15 at 13:29

27

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

answered Dec 26 '15 at 13:29

CularBytes

9,924
8
76
101

I have tried everything was mentioned here... but still its not working.. while reinstalling visual studio its works perfectly.. i thought missing dependencies is the reason.. – mansoor Dec 28 '15 at 05:01
if you've had a project that was working and fine and suddenly you got this issue then this is probably the fix! – Simon_Weaver Apr 26 '17 at 20:22

score 22 · Answer 5 · edited May 23 '17 at 12:10

22

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

edited May 23 '17 at 12:10

Community

1
1

answered Oct 31 '16 at 08:56

leyla azari

913
11
20

3

it works! looks like that visual studion thinks that System.Core has already been added but there really is not. So you need to do this manually – isxaker Jun 01 '17 at 10:51

score 12 · Answer 6 · answered Nov 01 '18 at 11:56

12

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

answered Nov 01 '18 at 11:56

Robo Burned

542
4
13

Worked for me Vs 2017 Asp MVC5 – Speuline May 15 '19 at 14:20
2

This one worked, VS 2019 & MVC5. I also cleaned out the bin/obj and .vs folders too. – Leniency Jun 14 '19 at 18:23
This solved my problem. thank you. – kisetu Mar 09 '22 at 08:28

score 7 · Answer 7 · edited Jul 10 '18 at 18:04

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.

edited Jul 10 '18 at 18:04

BurnsBA

4,347
27
39

answered Apr 05 '16 at 03:14

jsanman

71
1
1

please add tag with any technology or more .. No tags Found – Vikrant Kashyap Apr 05 '16 at 03:22
Adding the compilation/targetFramework attribute worked for me. – Tom Bowers Apr 17 '16 at 23:55
I had accidently added two different values for target framework, this solved my issue. – Geethanga Sep 02 '16 at 17:38
This fixed the problem for me, a hybrid asp.net/webforms app: I upgraded the target framework of my application to 4.7, did not notice these two web.config settings still pointing to 4.5. – Tom Regan Jul 10 '18 at 20:43

Angel Dinev · Answer 8 · 2017-12-12T17:54:44.377

6

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

edited Dec 12 '17 at 17:54

answered Dec 12 '17 at 15:14

Angel Dinev

399
4
13

1

While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - [From Review](/review/low-quality-posts/18232767) – Steve Dec 12 '17 at 17:00
1

@SteveG. Thanks, Steve! I've edited it. Haven't commented much before and lack some SO etiquette... :-) – Angel Dinev Dec 12 '17 at 18:05
1

This one solved my problem , I have to mention that a Visual Studio Restart also was needed, Thank You. – Saeed Mousavi Aug 27 '20 at 21:28

score 4 · Answer 9 · answered Aug 03 '16 at 08:17

4

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.

answered Aug 03 '16 at 08:17

Neshta

2,605
2
27
45

1

In my case, just close and restart VS. I have resharper but didn't need to do anything with it. – JayJay Oct 24 '16 at 14:08

score 4 · Answer 10 · answered May 14 '20 at 10:42

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>

score 3 · Answer 11 · answered Mar 13 '18 at 11:20

3

In Web.config I needed to change:

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

to

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

answered Mar 13 '18 at 11:20

juFo

17,849
10
105
142

1

Thank you, @juFo! This fixed it for me in Visual Studio 2019 with MVC 5. My MVC project's target framework was 4.7.2 while the web.config still had 4.7.1 for the ```targetFramework``` in the `````` and `````` tags. Simply updating the attribute to correctly reflect the project's .NET Framework version fixed it for me. – iCode Nov 06 '19 at 18:43

pkucas · Answer 12 · 2019-10-17T04:04:35.470

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

score 2 · Answer 13 · answered Nov 29 '15 at 18:59

2

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.

answered Nov 29 '15 at 18:59

Kevin R.

3,571
1
19
29

score 2 · Answer 14 · answered Jul 23 '18 at 12:08

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>

score 2 · Answer 15 · edited Feb 23 '20 at 10:07

2

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

edited Feb 23 '20 at 10:07

סטנלי גרונן

2,917
23
46
68

answered Feb 23 '20 at 09:47

Altaf

189
2
4

score 2 · Answer 16 · answered Apr 06 '20 at 10:03

2

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

answered Apr 06 '20 at 10:03

Nisanur

89
1
6

I do a lot of switching between versions of my project, a few that target different frameworks. This took care of my "System.Core" reference error. Thanks for the simple reminder that it is sometimes necessary to to clean up the VS environment between checkouts. – Suncat2000 May 26 '20 at 13:17

score 1 · Answer 17 · answered Jan 28 '16 at 00:25

1

Restarting Visual studio worked for me.

answered Jan 28 '16 at 00:25

Mangesh Kadam

69
1
6

This happened to me after some seemingly innocent NuGet updates. It was just libraries like jQuery and bootstrap. After the updates I got this error message and restarting Visual Studio fixed it. – Steve Hiner Apr 27 '16 at 22:43
I just did this and it worked, go figure. – Xavi Jan 17 '22 at 20:59

score 1 · Answer 18 · answered Jun 18 '16 at 20:24

1

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.

answered Jun 18 '16 at 20:24

Aggromonster

99
2
9

score 1 · Answer 19 · answered Feb 18 '18 at 08:42

1

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!

answered Feb 18 '18 at 08:42

Mehmet Taha Meral

3,315
28
30

I had 12 packages that needed to be upgraded and the sln ran without any problems once I updated everything. Thank you. – Jamie Nov 02 '18 at 15:48

score 0 · Answer 20 · answered Jan 03 '16 at 14:13

0

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

answered Jan 03 '16 at 14:13

Liam

5,033
2
30
39

Rogerio Picilli · Answer 21 · 2018-10-06T18:55:41.713

0

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

edited Oct 06 '18 at 18:55

answered May 05 '16 at 21:05

Rogerio Picilli

9
3

score 0 · Answer 22 · edited Jan 24 '17 at 09:32

0

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

edited Jan 24 '17 at 09:32

Owen Pauling

11,349
20
53
64

answered Aug 22 '16 at 03:59

maryam b

1

score 0 · Answer 23 · answered Nov 29 '16 at 23:47

0

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

answered Nov 29 '16 at 23:47

Jeph

455
2
8

score 0 · Answer 24 · answered Jan 05 '17 at 19:35

0

Try to add

using system.Linq.Expressions;

answered Jan 05 '17 at 19:35

user1223339

193
2
9

4

While this code snippet may solve the question, [including an explanation](http://meta.stackexchange.com/questions/114762/explaining-entirely-code-based-answers) really helps to improve the quality of your post. Remember that you are answering the question for readers in the future, and those people might not know the reasons for your code suggestion. – Farkie Jan 05 '17 at 20:11

score 0 · Answer 25 · answered Jan 24 '17 at 20:58

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?

score 0 · Answer 26 · answered Mar 30 '17 at 20:52

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.

score 0 · Answer 27 · answered May 07 '17 at 11:00

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!

score 0 · Answer 28 · answered Oct 27 '17 at 05:22

0

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.

answered Oct 27 '17 at 05:22

Sukesh Mullassery

11
2

score 0 · Answer 29 · answered Oct 14 '22 at 09:21

0

Installing the System.Core package with NuGet package manager works for me

answered Oct 14 '22 at 09:21

farukkayaduman

15
3

score 0 · Answer 30 · answered Dec 01 '22 at 15:48

In my case I checked the targetFramework of Microsoft.AspNet.Mvc in the packages.config file.

<package id="Microsoft.AspNet.Mvc" version="4.0.20710.0" targetFramework="net462" />

And I found that the targeting package was not installed.

After installing that targeting package, my issue was resolved.

score 0 · Answer 31 · answered Mar 31 '23 at 04:24

0

This worked for me in VS 2022:

Unload project
Reload project
Rebuild project/solution

answered Mar 31 '23 at 04:24

HOT theChunKk

181
6

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

31 Answers31

Linked