简体   繁体   English

"找不到 CodeDom 提供程序类型“Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider”"

[英]The CodeDom provider type "Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider" could not be located

If your project has Roslyn references<\/strong> and you are deploying it on an IIS server<\/strong> , you might get unwanted errors on the website as many hosting providers still have not upgraded their servers and hence do not support Roslyn.如果您的项目有Roslyn 引用<\/strong>,并且您将其部署在IIS 服务器上<\/strong>,您可能会在网站上收到不必要的错误,因为许多托管服务提供商仍未升级其服务器,因此不支持 Roslyn。

To resolve this issue, you will need to remove the Roslyn compiler from the project template<\/strong> .要解决此问题,您需要从项目模板中删除 Roslyn 编译器<\/strong>。 Removing Roslyn shouldn't affect your code's functionality.删除 Roslyn 不应影响代码的功能。 It worked fine for me and some other projects (C# 4.5.2) on which I worked.它对我和我工作的其他一些项目(C# 4.5.2)来说工作得很好。

Do the following steps:执行以下步骤:

  1. Remove from following Nuget Packages using command line shown below ( or you can use GUI of Nuget Package manager by Right Clicking on Root Project Solution and removing them<\/em> ).使用如下所示的命令行从以下 Nuget 包中删除(或者您可以通过右键单击根项目解决方案并删除它们来使用 Nuget 包管理器的 GUI<\/em> )。

     PM> Uninstall-package Microsoft.CodeDom.Providers.DotNetCompilerPlatform PM> Uninstall-package Microsoft.Net.Compilers<\/code><\/pre><\/li>
  2. Remove the following code from your Web.Config file and restart IIS<\/strong> .从您的 Web.Config 文件中删除以下代码并重新启动 IIS<\/strong> 。 ( Use this method only if step 1 doesn't solve your problem.<\/em> ) 仅当步骤 1 不能解决您的问题时才使用此方法。<\/em> )

     <system.codedom> <compilers> <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="\/langversion:6 \/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.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="\/langversion:14 \/nowarn:41008 \/define:_MYTYPE=\\&quot;Web\\&quot; \/optionInfer+" \/> <\/compilers><\/code><\/pre>

    <\/li><\/ol>"

Be careful of following this answer's advice.<\/strong>请注意遵循此答案的建议。<\/strong> While it solves the problem at hand, it might cause different problems at a later date.<\/strong>虽然它解决了手头的问题,但它可能会在以后导致不同的问题。<\/strong>

<\/blockquote>

I got the same problem.我遇到了同样的问题。 Apparently the .NET compiler was not loaded to the GAC<\/code> .显然 .NET 编译器没有加载到GAC<\/code> 。 What I did to solve it was:我为解决它所做的是:

First, in the package manager console type:首先,在包管理器控制台中输入:

 PM> Install-Package Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code><\/pre>

Now, for some reason the nice gentlemen in Microsoft have decided not to install it to the GAC for us.现在,出于某种原因,微软的好先生们决定不为我们将它安装到 GAC。 You can do it manually by opening the Developer Command Prompt and typing:您可以通过打开开发人员命令提示符并键入以下内容手动执行此操作:

 gacutil -i "C:\\*PATH TO YOUR APP CODE*\\bin\\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.dll"<\/code><\/pre>

Conclusion结论<\/h2>

Microsoft try to encourage everyone to do everything with nugets which could be fine without the occasional bugs you run into with the nuget system.微软试图鼓励每个人都使用 nugets 做所有事情,如果没有你在 nuget 系统中偶尔遇到的错误,这可能会很好。 Try to use the same project on different solutions, accidentally (or not) update one of the many nugets it uses on one of them, and if you are unlucky you'll see what I mean when you try to build the other solution.尝试在不同的解决方案上使用相同的项目,不小心(或不)更新它在其中一个上使用的众多 nuget 之一,如果你不走运,当你尝试构建另一个解决方案时,你会明白我的意思。 On the other hand, putting files in the GAC can also cause future problems since people tend to forget what they put there and then when setting up new environments they forget to include these files.另一方面,将文件放入 GAC 也会导致未来的问题,因为人们往往会忘记放在那里的内容,然后在设置新环境时忘记包含这些文件。 Another possible solution is to put the files in a central folder for 3rd party dlls (even though it's strange to call the compiler 3rd party), which creates problems of broken references when setting up new environments.另一种可能的解决方案是将文件放在第 3 方 dll 的中央文件夹中(即使将编译器称为第 3 方很奇怪),这会在设置新环境时造成引用损坏的问题。 If you decide to install the dll to the GAC, use caution and remember that you did so.如果您决定将 dll 安装到 GAC,请谨慎行事并记住您这样做了。 If you don't, download the nuget for each project again and bear all the annoying bugs being caused by it (at least used to happen when I finally got sick of it and just placed the files in the GAC).如果不这样做,请再次下载每个项目的 nuget,并承担由它引起的所有烦人的错误(至少在我最终厌倦它并将文件放入 GAC 时曾经发生过)。 Both approaches might give you headaches and create problems, it's just a question of which problems you prefer to deal with.这两种方法都可能让您头疼并产生问题,这只是您更喜欢处理哪些问题的问题。 Microsoft recommends to use the nuget system, and generally, it's better to listen to them than to an unknown programmer in SO, unless you are completely sick of the nuget system and used to deal with the GAC long enough for it to be a better alternative for you. Microsoft 建议使用 nuget 系统,一般来说,最好听他们而不是 SO 中不知名的程序员,除非你完全厌倦了 nuget 系统并且习惯与 GAC 打交道的时间足够长,以使其成为更好的选择为你。

"

Just add the next nuget package to your project - Microsoft.CodeDom.Providers.DotNetCompilerPlatform .只需将下一个 nuget 包添加到您的项目 - Microsoft.CodeDom.Providers.DotNetCompilerPlatform

Had the same problem.有同样的问题。

I have the same problem that my app worked in Vs2013 but getting the error after updating to Vs2015.我的应用程序在 Vs2013 中运行时遇到相同的问题,但在更新到 Vs2015 后出现错误。

  1. In Vs2015, right click project's References folder, to open NuGet Package Manager在 Vs2015 中,右键单击项目的 References 文件夹,打开 NuGet 包管理器<\/li>
  2. Under Browse tab, search for "DotNetCompilerPlatform" and install "Microsoft.CodeDom.Providers.DotNetCompilerPlatform" lib在浏览选项卡下,搜索“DotNetCompilerPlatform”并安装“Microsoft.CodeDom.Providers.DotNetCompilerPlatform”库<\/li><\/ol>"

I know it's an old thread, but I'd like to point the possible version issue of DotNetCompilerPlatform.dll, f.我知道这是一个旧线程,但我想指出 DotNetCompilerPlatform.dll,f 的可能版本问题。 ex.前任。 after an update.更新后。 Please check, if the new generated Web.config file is different as your released web.config, in particular the system.codedom part.请检查新生成的 Web.config 文件是否与您发布的 web.config 不同,尤其是 system.codedom 部分。 In my case it was the version change from 1.0.7 to 1.0.8.就我而言,这是从 1.0.7 到 1.0.8 的版本更改。 The new dll had been already copied to the server, but I didn't change the old web.config (with some server special settings):新的 dll 已经复制到服务器,但我没有更改旧的 web.config(带有一些服务器特殊设置):

<pre>
  <system.codedom>
    <compilers>
      <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.8.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.8.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:41008 /define:_MYTYPE=\&quot;Web\&quot; /optionInfer+" />
    </compilers>
  </system.codedom>
</pre>

After I update the two lines, the error disappeared.更新这两行后,错误消失了。

Another possible solution:<\/strong>另一种可能的解决方案:<\/strong>

➜ Restart your Visual Studio Instance with Administrator Rights<\/strong> ➜ 使用管理员权限<\/strong>重新启动您的 Visual Studio 实例

在此处输入图像描述<\/a>

"

According to your repro steps, I assumed that changing the output path in the application's property was your only change after you created the application.根据您的复制步骤,我假设更改应用程序属性中的输出路径是您创建应用程序后唯一的更改。 The only thing this change does is that it tells Visual Studio to put the output assemblies of MSBuild into the new folder.此更改所做的唯一事情是它告诉 Visual Studio 将 MSBuild 的输出程序集放入新文件夹中。 At runtime, however, ASP.Net wouldn't have any idea that it should load assemblies from this new folder instead of the \\bin folder.然而,在运行时,ASP.Net 不知道它应该从这个新文件夹而不是 \\bin 文件夹加载程序集。

This answer<\/a> shows the way to change the build output directory of a WebApi application.答案<\/a>显示了更改 WebApi 应用程序的构建输出目录的方法。 To get the exact same error showed in that post, you need to comment out the entire <system.codedom> section in web.config.要获得该帖子中显示的完全相同的错误,您需要注释掉 web.config 中的整个 <system.codedom> 部分。 And then you can follow the instructions to change the output path.然后您可以按照说明更改输出路径。

After you get your applicaiton work, you may then uncomment the <system.codedom> section.完成应用程序后,您可以取消注释 <system.codedom> 部分。 If you don't use C# 6 new syntax in your application at all you can uninstall the Microsoft.CodeDom.Providers.DotNetCompilerPlatform from you application;如果您在应用程序中根本不使用 C# 6 新语法,则可以从应用程序中卸载 Microsoft.CodeDom.Providers.DotNetCompilerPlatform; otherwise, you may want to add the following command line in your post-build event,否则,您可能需要在构建后事件中添加以下命令行,

xcopy /Q /Y "$(TargetDir)roslyn\*.*" "$(TargetDir)..\roslyn\"

Easy way - Project > Manage NuGet Packages... > Browse(tab) > in search input set this: Microsoft.CodeDom.Providers.DotNetCompilerPlatform简单的方法-项目>管理NuGet包...>浏览(选项卡)>在搜索输入中设置:Microsoft.CodeDom.Providers.DotNetCompilerPlatform

You can install or update or uninstall and install this compiler您可以安装或更新或卸载并安装此编译器

点网编译器平台

In my case, this happened when i change the permission of application folder and account IIS_IUSRS has been removed.就我而言,这发生在我更改应用程序文件夹的权限并且帐户 IIS_IUSRS 已被删除时。 After i re-added IIS_IUSRS (IIS Manager-> YourWebApp -> Edit Permission -> Add IIS_IUSRS) to the application folder and its worked.在我将 IIS_IUSRS(IIS 管理器 -> YourWebApp -> 编辑权限 -> 添加 IIS_IUSRS)重新添加到应用程序文件夹后,它就可以工作了。

"

It stopped after publishing on the production server.它在生产服务器上发布后停止。 The reason why it showed me this error was because it was deployed to a sub folder.它向我显示此错误的原因是因为它已部署到文件夹。 In IIS i clicked right on the subfolder and excuted "Convert to application" and after this it worked.在 IIS 中,我在子文件夹上单击鼠标右键并执行“转换为应用程序”,然后它就起作用了。

Here's how I resolved it:这是我解决它的方法:

  1. Deleted the bin folder in the project directory.删除了项目目录下的bin文件夹。
  2. Click on Build Solution .单击Build Solution In VS2017(Run as Admin) > Build > Build Solution .VS2017(以管理员身份运行)> 构建 > 构建解决方案

Then the problem came back.然后问题又来了。 I uninstalled both Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code> and Uninstall-package Microsoft.Net.Compilers<\/code> but no help.我卸载了Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code>和Uninstall-package Microsoft.Net.Compilers<\/code>但没有帮助。 Then installed - no help.然后安装 - 没有帮助。 Cleaned project and built no help.清理项目并没有帮助。 Restarted server no help.Then I noticed the project needed not the latest one which is currently 1.0.5 but 1.0.3 as that was the error could not load the 1.0.3 version.重新启动服务器没有帮助。然后我注意到该项目不需要当前是 1.0.5 而是 1.0.3 的最新项目,因为这是错误无法加载 1.0.3 版本。 So I installed that dll version instead and now it works.所以我安装了那个 dll 版本,现在它可以工作了。

"

如果您使用的是 git,您可能会忽略提交中的 .dll

ASP.NET does not search bin\/debug<\/code> or any subfolder under bin for assemblies like other types of applications do. ASP.NET 不会像其他类型的应用程序那样在bin\/debug<\/code>或 bin 下的任何子文件夹中搜索程序集。 You can instruct the runtime to look in a different place using the following configuration:您可以使用以下配置指示运行时查看不同的位置:

<configuration>
   <runtime>   
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <probing privatePath="bin;bin\Debug;bin\Release"/>
      </assemblyBinding>
   </runtime>   
</configuration>

I had a number of projects in the solution and the web project (problem giving this error) was not set as the StartUp project.我在解决方案中有许多项目,并且 Web 项目(出现此错误的问题)未设置为 StartUp 项目。 I set this web project as the StartUp project, and clicked on the menu item "Debug"->"Start Debugging" and it worked.我将此Web项目设置为启动项目,然后单击菜单项“调试”->“开始调试”,它就可以工作了。 I stopped debugging and then tried it again and now it's back working.我停止调试,然后再次尝试,现在它又恢复了。 Weird.奇怪的。

just uninstall the package from package manager console from command below只需从下面的命令从包管理器控制台卸载包

PM> Uninstall-package Microsoft.CodeDom.Providers.DotNetCompilerPlatform PM> 卸载包 Microsoft.CodeDom.Providers.DotNetCompilerPlatform

PM> Uninstall-package Microsoft.Net.Compilers PM> 卸载包 Microsoft.Net.Compilers

and then install it again from nuget manager然后从 nuget manager 再次安装在此处输入图像描述

您应该更新项目中的“Microsoft.CodeDom.Providers.DotNetCompilerPlatform”和“Microsoft.Net.Compilers”包。

"

In my case, I got the error when I had my Web Application in 4.5.2 and the referenced class libaries in 4.6.1.就我而言,当我在 4.5.2 中使用 Web 应用程序并在 4.6.1 中使用引用的类库时出现错误。 When I updated the Web Application to 4.5.2 version the error went away.当我将 Web 应用程序更新到 4.5.2 版本时,错误消失了。

I was getting this error because my application pool user was set to ApplicationPoolIdentity.我收到此错误是因为我的应用程序池用户设置为 ApplicationPoolIdentity。 I changed it to a user\/service account that has access to the folder and the error went away.我将其更改为有权访问该文件夹的用户\/服务帐户,错误就消失了。

"

Here are my findings.这是我的发现。 I also faced this problem today's morning.今天早上我也遇到了这个问题。 I just added my current user to application pool on which application was running.我刚刚将当前用户添加到正在运行应用程序的应用程序池中。

Steps:脚步:

  1. Open IIS打开 IIS

  2. Click on application pool单击应用程序池

  3. Select your application pool on which you are getting problem选择您遇到问题的应用程序池

  4. Right Click -> advanced settings右键->高级设置

  5. Click on three dot icon beside the identiy点击身份旁边的三点图标

  6. Now select custom account现在选择自定义帐户

  7. Give your PC user name and Password提供您的 PC 用户名和密码

  8. Save保存

Refresh your application.. and it will start working.刷新您的应用程序..它将开始工作。 There was some security issue for accessing dll.访问 dll 存在一些安全问题。

If you have recently installed or updated the Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code> package, double-check that the versions of that package referenced in your project point to the correct, and same, version of that package:如果您最近安装或更新了Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code>包,请仔细检查项目中引用的该包的版本是否指向该包的正确且相同的版本:

  • In ProjectName.csproj<\/code> , ensure that an <Import><\/code> tag for Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code> is present and points to the correct version.ProjectName.csproj<\/code>中,确保Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code>的<Import><\/code>标记存在并指向正确的版本。

    <\/li>

  • In ProjectName.csproj<\/code> , ensure that a <Reference><\/code> tag for Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code> is present, and points to the correct version, both in the Include<\/code> attribute and the child <HintPath><\/code> .ProjectName.csproj<\/code>中,确保Microsoft.CodeDom.Providers.DotNetCompilerPlatform<\/code>的<Reference><\/code>标记存在,并在Include<\/code>属性和子<HintPath><\/code>中指向正确的版本。

    <\/li>

  • In that project's web.config<\/code> , ensure that the <system.codedom><\/code> tag is present, and that its child <compiler><\/code> tags have the same version in their type<\/code> attribute.在该项目的web.config<\/code>中,确保存在<system.codedom><\/code>标记,并且其子<compiler><\/code>标记在其type<\/code>属性中具有相同的版本。

    <\/li><\/ul>

    For some reason, in my case an upgrade of this package from 1.0.5 to 1.0.8 caused the <Reference><\/code> tag in the .csproj<\/code> to have its Include<\/code> pointing to the old version 1.0.出于某种原因,在我的情况下,将此包从 1.0.5 升级到 1.0.8 导致.csproj<\/code>中的<Reference><\/code>标记使其Include<\/code>指向旧版本 1.0。 5<\/strong> .0 (which I had deleted after upgrading the package), but everything else was pointing to the new and correct version 1.0. 5<\/strong> .0(我在升级软件包后删除了它),但其他所有内容都指向新的正确版本 1.0。 8<\/strong> .0. 8<\/strong> .0。

    "

Make sure your project has fully built!确保您的项目已完全构建!<\/h3>

Click on 'Output' tab and make sure you don't have something like:单击“输出”选项卡并确保您没有类似的内容:

========== Rebuild All: 14 succeeded, 1 failed, 0 skipped ========= ========== 全部重建:14 个成功,1 个失败,0 个跳过 =========

<\/blockquote>

And open your bin<\/code> folder and check to see if it's up to date.并打开您的bin<\/code>文件夹并检查它是否是最新的。

I had a whole bunch of typescript errors that I ignored at first, forgetting that they were breaking the build and leading to there being no DLLs copied in.我一开始忽略了一大堆打字稿错误,忘记了它们破坏了构建并导致没有复制 DLL。

"

从启动命令转到 inetmgr 在 IIS 管理器控制台中,选择默认网站下的应用程序文件夹,右键单击该文件夹,然后转换为应用程序通过启用运行 .asmx 文件它解决了问题

"

添加对 CppCodeProvider 程序集的引用。

在我的情况下,我的 Web 项目没有正确加载(它显示项目不可用),然后我不得不在以管理员模式打开我的 Visual Studio 后重新加载我的 Web 项目,然后一切正常。

"

If you have been working on a project and this just now popped up as an error.如果您一直在从事一个项目,而这刚刚作为错误弹出。 REBOOT your computer (or server in my case) this fixed the issue for me.重新启动您的计算机(或在我的情况下为服务器)这为我解决了这个问题。

"

我只是遇到了同样的问题,这是因为我移动了项目位置,只需要重新创建虚拟目录。

"

The exception that we ran into was not on the local but on the remote server, the Azure CI was reading it from the packages folder but the compiler versions mentioned above were not found.我们遇到的异常不在本地,而是在远程服务器上,Azure CI 正在从包文件夹中读取它,但找不到上面提到的编译器版本。

To fix this we modified the project file to make it something like为了解决这个问题,我们修改了项目文件,使其类似于

It is not referencing any of the packages here directly referencing the environment variables.它没有引用此处直接引用环境变量的任何包。

This fixed the issue, however in our cases we don't use packages directly from "package.config" instead we have a separate folder to maintain version integrity across teams.这解决了这个问题,但是在我们的案例中,我们不直接使用“package.config”中的包,而是有一个单独的文件夹来维护跨团队的版本完整性。

"

检查文件中的BIN文件夹是否完整上传或丢失。

Regarding this error I've tried:关于这个错误我试过:

If you see this probably you are building in release mode .如果您看到这可能是您正在构建发布模式 For production you should publish instead of building in release mode.对于生产,您应该发布而不是在发布模式下构建。 For local development build in debug mode.对于本地开发调试模式构建。

In our case we are using ToroiseSVN and it seems by default the bin folder is not added to the sourcecontrol.在我们的例子中,我们使用的是 ToroiseSVN,似乎默认情况下 bin 文件夹没有添加到源代码控制中。 So when updating the website on the production server the bin folder was not added to it, thus resulting in this exception.因此,在生产服务器上更新网站时,没有将 bin 文件夹添加到其中,从而导致此异常。

To add the bin folder to SVN go to the folder on the hdd and find the bin folder.要将 bin 文件夹添加到 SVN,请转到硬盘上的文件夹并找到 bin 文件夹。 Right click it and select TortoiseSVN --> Add右键单击它并选择 TortoiseSVN --> 添加

Now update the repository to include the newly added files and update the production server next.现在更新存储库以包含新添加的文件,然后更新生产服务器。 All should be well now.现在一切都应该好了。

Ensure Internet Information Services(IIS) is enabled in Windows features on your machine. 确保计算机的Windows功能中启用了Internet信息服务(IIS)。 在此处输入图片说明

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 无法找到CodeDom提供程序类型“Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider ...” - The CodeDom provider type “Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider …” could not be located Microsoft.CodeDom.Providers.DotNetCompilerPlatform 的问题 - Problem with Microsoft.CodeDom.Providers.DotNetCompilerPlatform 无法加载文件或程序集“Microsoft.CodeDom.Providers.DotNetCompilerPlatform 或其依赖项之一。” 访问被拒绝 - Could not load file or assembly 'Microsoft.CodeDom.Providers.DotNetCompilerPlatform or one of its dependencies. Access is denied 有没有办法在没有 nuget package 的情况下使用 Microsoft.CodeDom.Providers.DotNetCompilerPlatform? - Is there a way to use Microsoft.CodeDom.Providers.DotNetCompilerPlatform without a nuget package? 无法找到 CodeDom 提供程序类型“Microsoft.VisualC.CppCodeProvider”,尝试编译 node_modules - CodeDom provider type 'Microsoft.VisualC.CppCodeProvider' could not be located, trying to compile node_modules Web 应用程序构建错误:无法找到 CodeDom 提供程序类型 Microsoft.VisualC.CppCodeProvider - Web Application Build Error: The CodeDom provider type Microsoft.VisualC.CppCodeProvider could not be located 使用“ Microsoft.CodeDom.Providers.DotNetCompilerPlatform”包时,csc.exe编译时间降低 - csc.exe compilation time degradation when “Microsoft.CodeDom.Providers.DotNetCompilerPlatform” package is used 找不到 ASP.NET CodeDom 提供程序错误 - ASP.NET CodeDom provider could not be located error 如何修复配置错误“无法找到 CodeDom 提供程序类型”和解析错误“无法加载类型”导致彼此? - How to fix configuration error 'The CodeDom provider type could not be located' and parsing error 'Could not load type' leading to each other? .Net / IIS服务器错误-找不到CodeDOM提供程序类型 - .Net / IIS server error - CodeDOM Provider Type Could Not Be Found
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM