Could not load file or assembly 'Microsoft.CodeDom.Providers.DotNetCompilerPlatform

4

Other articles on here haven't been able to solve my issue. The following errors are being thrown when I run my ASP.NET MVC5 Web Project.

Anyone got an idea where I am going wrong?

Could not load file or assembly 'Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.8.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)



=== Pre-bind state information ===
LOG: DisplayName = Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.8.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 (Fully-specified)
LOG: Appbase = file:///C:/Users/Teije/Documents/git/Project2.2/HaarlemFestival-Web/
 LOG: Initial PrivatePath =         C:\Users\Teije\Documents\git\Project2.2\HaarlemFestival-Web\bin
Calling assembly : (Unknown)
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Users\Teije\Documents\git\Project2.2\HaarlemFestival-Web\web.config
LOG: Using host configuration file: C:\Users\Teije\Documents\IISExpress\config\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Post-policy reference:     Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.8.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
LOG: Attempting download of new URL file:///C:/Users/Teije/AppData/Local/Temp/Temporary ASP.NET Files/vs/b2d7334d/e3876cf7/Microsoft.CodeDom.Providers.DotNetCompilerPlatform.DLL.
LOG: Attempting download of new URL file:///C:/Users/Teije/AppData/Local/Temp/Temporary ASP.NET     Files/vs/b2d7334d/e3876cf7/Microsoft.CodeDom.Providers.DotNetCompilerPlatform/Microsoft.CodeDom.Providers.DotNetCompilerPlatform.DLL.
LOG: Attempting download of new URL file:///C:/Users/Teije/Documents/git/Project2.2/HaarlemFestival-    Web/bin/Microsoft.CodeDom.Providers.DotNetCompilerPlatform.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Build Number
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.
asp.net
visual-studio
asp.net-mvc-5
asked on Stack Overflow Jan 31, 2018 by Teije

3 Answers

6

We just had this error in one of our test environments. The problem was in the web.config file. The section had settings to reference the DotNetCompilerPlatform assembly, but had the wrong version number. We updated web.config to the proper version number and it fixed the error.

<compilers>
  <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:1659;1699;1701" />
  <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:41008 /define:_MYTYPE=\&quot;Web\&quot; /optionInfer+" />
</compilers>
answered on Stack Overflow May 2, 2019 by mhenrickson
4

This Problem Happens From Your Nuget package Microsoft.CodeDom.Providers.DotNetCompilerPlatform. It Is Wrong Version. Remover Current Version On Your Project Then Install Again From Nuget packet.

answered on Stack Overflow Jun 26, 2018 by Mahmoud Valizadeh
0

It can also happen if your target folder is something other than "bin/". Roslyn by default looks for the "roslyn" folder in the "bin" folder, so if you are compiling, for example, to "bin/debug/", there may not be a roslyn folder there, and thus it can't find the provider.

You can fix this by reverting to a plain "bin/" target, or by ensuring that a full roslyn folder is copied across to the "bin/debug/" folder as a Post-Build event. Because a publish always pushes to the correct target folder despite the compilation target folder of your build machine, that's why it fails when you run locally, but works if you deploy it.

(Some people have the opposite problem, it working locally, but fails when deployed to IIS, because IIS doesn't have a copy of the CodeDom provider in its GAC, but that's a totally different issue.)

answered on Stack Overflow Aug 22, 2019 by Jeff Woods

User contributions licensed under CC BY-SA 3.0