blocks|key|929949|text|向web.config文件的“batch=”元素添加编译“false”属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|929950|出现此问题的原因是ASP.NET+2.0使用应用程序引用和应用程序的文件夹结构来编译应用程序的方式。如果应用程序的web.config文件中元素的batch属性设置为true，则ASP.NET+2.0会将应用程序中的每个文件夹编译为单独的程序集。|929951|http://www.sellsbrothers.com/1995|offset|length|929952|http://support.microsoft.com/kb/919284|929953|entityMap|0|LINK|mutability|MUTABLE|url|http://sellsbrothers.com/1995|1^0|0|0|0|X|0|0|0|12|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@$F|V|G|W|1|X]]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|I]]]]

Add the batch="false" attribute to the "compilation" element of the web.config file.

This problem occurs because of the way in which ASP.NET 2.0 uses the application references and the folder structure of the application to compile the application. If the batch property of the element in the web.config file for the application is set to true, ASP.NET 2.0 compiles each folder in the application into a separate assembly.

<a href="http://sellsbrothers.com/1995" rel="noreferrer">http://www.sellsbrothers.com/1995</a>

<a href="http://support.microsoft.com/kb/919284" rel="noreferrer">http://support.microsoft.com/kb/919284</a>

blocks|key|3344067|text|作为另一个数据点，我只是遇到了这个问题，没有任何关于循环引用的证据，正如Ben答案中的链接所描述的那样。构建我的网站项目将会失败，因为有一些这样的错误，设置compilation+batch="false"可以修复它，但我不想走那条路，因为这是一个大型的生产网站。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3344068|此解决方案位于我的D:\svn文件夹的子文件夹中，我已将其映射到S：。当我从S:打开解决方案时，出现了这些错误，但如果我直接转到D:\svn并打开解决方案，则没有错误。|3344069|我还注意到，尽管我的web.config中有compilation+batch="true"，但当从映射的S:+drive打开解决方案时，我所有的.ascx文件都被编译到它们自己的程序集中。如果我从物理位置打开它，.ascx文件将被编译到各自文件夹的程序集中(这就是batch="true"的工作方式)。|3344070|真奇怪。|3344071|entityMap^0|26|P|0|0|M|O|3P|C|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|M|$]]

As another data point, I just had this problem without any evidence of circular references as described in the links in Ben's answer. Building my web site project would fail with a few of these errors, and setting <code>compilation batch="false"</code> fixed it, but I didn't want to go that route as this is a large-ish production website.

This solution was in a subfolder of my D:\svn folder, which I had mapped to S:. When I opened the solution from S:, these errors occurred, but if I went straight to D:\svn and opened the solution, no errors. 

I also noticed that, despite having <code>compilation batch="true"</code> in my web.config, when opening the solution from the mapped S: drive all my .ascx files get compiled into their own assemblies. If I open it from the physical location, the .ascx files get compiled into their respective folders' assemblies (which is how <code>batch="true"</code> is supposed to work).

Strange.

blocks|key|3344109|text|此错误是由于web表单的类名与具有相同类名的wsdl存根(文件.cs后面的代码)之间的冲突造成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3344110|ASPX页面:仪表板类:+partiacl类仪表板|3344111|AppCode/APIServices.cs:公共分部类仪表板|3344112|错误仅在发布网站时可重现，但构建和调试未通知任何错误。|3344113|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

This error was due to conflict between class name of web form and wsdl stub(code behind file .cs) having the same class name i.e.

ASPX page: Dashboard 
Class: partiacl class Dashboard

AppCode/APIServices.cs: public partial class Dashboard 

Error was reproducible only on publishing the website but build and debug did not inform any error.

blocks|key|126242|text|在我的例子中，当我编辑一个仍然具有重复类名的Designer.cs文件时，这个问题就解决了。由于某些原因，当我将类"logout“重命名为"logout2”时，在设计器文件中它并没有自动更改，仍然是"logout"，并且这个类名已经存在于我的项目中的一个预编译的dll中(它属于我使用并开发的一个第三方web应用程序)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126243|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, the problem was solved when I edited a Designer.cs file that still had the duplicated class name. for some reason, when i renamed the class "logout" to "logout2", in the designer file it was not automatically changed, and was still "logout", and this class name already existed in a precompiled dll in my project (that belongs to a third party web app that I work with and develop around of).

blocks|key|126268|text|此错误的一个可能原因是，有2个aspx页面在其<@page+language=......inherits=>行的inherits=中具有相同的名称。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|126269|更改inherits=名称可解决此错误。|126270|entityMap^0|N|W|1L|9|0|2|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

One possible reason for this error is that there are 2 aspx pages which are having the same name in their <code>inherits=</code> in the <code>&lt;@page language=......inherits=&gt;</code> line.

Changing the <code>inherits=</code> name solves the error.

blocks|key|4189640|text|在将aspx页的一部分放入单独的用户控件时遇到此问题。在我的机器上一切正常，在服务器上得到一个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4189641|重命名了问题类和文件。|offset|length|style|BOLD|4189642|http://support.microsoft.com/kb/919284方法2:对应用程序中的文件夹重新排序关于可能的循环引用|4189643|entityMap|0|LINK|mutability|MUTABLE|url|http://support.microsoft.com/kb/919284^0|0|0|B|0|0|12|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Got this problem when put a part of an aspx page into the separate user control. On my machine everything was fine, on the server got an error.

Renamed the problem class and file.

<a href="http://support.microsoft.com/kb/919284" rel="nofollow">http://support.microsoft.com/kb/919284</a> Method 2: Reorder the folders in the application is writing about possible circular references

blocks|key|3344272|text|在我的例子中，我重命名了一个项目，所以dll也被重命名了。当我只是复制了新的dll，但没有考虑从服务器上删除旧的dll时，我很快就有了一对同名的类。删除过时的dll正在起作用(当然)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3344273|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case I had renamed a project, so also the dll had been renamed. When I just copied the new dll but didn't think of deleting the old one from the server, I soon had a bunch of pairs of classes with the same names. Deleting the outdated dll's was doing the trick (of cause).

blocks|key|126373|text|有时，删除解决方案并重新创建它可能会有所帮助。由于从VS2005转换到vs2010时会发生这种使用，因此解决方案中保留了对Framework4.0的一些引用(升级后)，即使所有项目都被定义为3.5。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126374|正常情况下，重新构建解决方案应该可以解决这些问题。|126375|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Sometimes it may help to remove the solution and create it again.
Since this use to happen when converted from VS2005 to vs2010 some references to framework 4.0 (after upgrading ) remains in the solution, even all projects are defined as 3.5.

Normally rebuilding the solution should clear these problems.

blocks|key|930144|text|在我的例子中，从解决方案中所有项目的bin文件夹中删除所有输出程序集解决了这个问题。不幸的是，我对此没有任何解释。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|930145|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case deleting all output assemblies from bin folders in all projects in the solution solved the issue. Unfortunately I have no explanation for it.

blocks|key|3344371|text|当我在编译服务器上编译应用程序时，我遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3344372|我的控制器有一个简单的静态代码，所以我改变了我的ascx：|3344373|+<%25@+Control+Language="C#"+AutoEventWireup="true"+CodeBehind="controllerName.ascx.cs"+Inherits="Controls.controllerName"+%25>|code-block|syntax|javascript|3344374|至|3344375|+<%25@+Control+Language="C#"+AutoEventWireup="true"+Src="controllerName.ascx.cs"+Inherits="Controls.controllerName"+%25>|3344376|此外，还从codebehind中删除了partial关键字，并向codebehind添加了一个命名空间。|3344377|这一点：|3344378|using+System;
using+System.Web.UI;

///+<summary>
///+My+controller
///+</summary>
public+partial+class+controllerName:+UserControl
{
++++protected+void+Page_Load(object+sender,+EventArgs+e)
++++{
++++}
}|3344379|要这样做：|3344380|using+System;
using+System.Web.UI;

namespace+Controles
{
++++///+<summary>
++++///+My+controller
++++///+</summary>
++++public+class+controllerName+:+UserControl
++++{
++++++++protected+void+Page_Load(object+sender,+EventArgs+e)
++++++++{
++++++++}
++++}
}|3344381|这对我很管用。|3344382|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|17|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|19|8|@]|9|@]|A|$G|H]]|$1|W|3|X|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

I had the same problem when I was compiling the application on a compiling server.

My controller had a simple static code, so I changed my ascx:

<pre><code> &lt;%@ Control Language="C#" AutoEventWireup="true" CodeBehind="controllerName.ascx.cs" Inherits="Controls.controllerName" %&gt;
</code></pre>

To

<pre><code> &lt;%@ Control Language="C#" AutoEventWireup="true" Src="controllerName.ascx.cs" Inherits="Controls.controllerName" %&gt;
</code></pre>

Also removed the partial keyword from the codebehind and added a namespace to the codebehind.

This:

<pre><code>using System;
using System.Web.UI;

/// &lt;summary&gt;
/// My controller
/// &lt;/summary&gt;
public partial class controllerName: UserControl
{
 protected void Page_Load(object sender, EventArgs e)
 {
 }
}
</code></pre>

To this:

<pre><code>using System;
using System.Web.UI;

namespace Controles
{
 /// &lt;summary&gt;
 /// My controller
 /// &lt;/summary&gt;
 public class controllerName : UserControl
 {
 protected void Page_Load(object sender, EventArgs e)
 {
 }
 }
}
</code></pre>

And that worked for me.

blocks|key|3344409|text|如果您将.cs文件放在App_Code中，并将其生成操作更改为在Web应用程序项目中编译，则可能会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3344410|将App_Code中的.cs文件的构建操作作为内容，或者将App_Code的名称更改为其他名称。我更改了名称，因为智能感知不会修复标记为内容的.cs文件。|3344411|欲了解更多信息，请访问http://vishaljoshi.blogspot.se/2009/07/appcode-folder-doesnt-work-with-web.html|offset|length|3344412|entityMap|0|LINK|mutability|MUTABLE|url|http://vishaljoshi.blogspot.se/2009/07/appcode-folder-doesnt-work-with-web.html^0|0|0|B|27|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

This might happen if you place .cs files in App_Code and changed their build action to compile in a Web Application Project.

Either have the build action for the .cs files in App_Code as Content or change the name of App_Code to something else. I changed the name since intellisense won't fix .cs files marked as content.

More info at <a href="http://vishaljoshi.blogspot.se/2009/07/appcode-folder-doesnt-work-with-web.html">http://vishaljoshi.blogspot.se/2009/07/appcode-folder-doesnt-work-with-web.html</a>

blocks|key|925438|text|对于我来说，当我将我的预编译set+/Publish位置设置为当前目录时，就会发生这种情况，这也是站点的根文件夹所在的目录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|925439|然后，我的Web站点在编译/构建时将发布文件夹视为项目的一部分，然后以这种方式查找重复项。|925440|也就是说，不要将站点的已发布/预编译版本放在站点的代码文件夹中。|925441|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

For me this happened when I had my PrecompiledWeb/Publish location set to the current directory which was where the site's root folder was too.

My Web Site was then seeing the publish folder as part of the project when compiling/building and then finding duplicates in that manner.

i.e. Don't put the published/precompiled version of your site in your site's code folders.

blocks|key|4189940|text|我在编译时遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4189941|我同意batch="true"属性，错误提示存在2个程序集|offset|length|style|BOLD|4189942|解决方案1:删除其中一个|4189943|Solution2:配置其中之一|4189944|entityMap^0|0|3|C|0|0|6|0|0|A|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|M|$]]

I faced with the problem in compile time.

I agree with the batch="true" attributes, error is telling there exist 2 assembly

Solution 1: deleting one of them

Solution2: Configure one of them

blocks|key|126606|text|这些答案对我都不起作用，但我确实解决了这个问题。由于我使用的是VS的发布功能来部署web应用程序，因此我在Publish+Web向导中选择了在发布之前删除所有现有文件的选项。这迫使应用程序有一个干净的副本，从那时起一切都很正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126607|如果您的本地调试副本运行良好，但发布的系统运行不正常，则此解决方案可能会有所帮助。如果您不想花时间跟踪要删除的单个dll，也不介意首先删除生产文件，则此解决方案非常有用。|126608|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

None of these answers worked for me, however I did fix the problem. Since I was using VS's Publish function to deploy the web application, I selected the option to delete all existing files prior to publish in the Publish Web wizard. This forced a clean copy of the application and everything worked fine from there.

This solution might be helpful if your local debugging copy works fine but published system isn't. Also great if you don't want to take the time to track down individual dlls to delete and don't mind the production files being deleted first.

blocks|key|3344522|text|如果DLL显示在临时文件夹中，则应尝试清理解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3344523|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If the DLL's are showing in a temporary folder, you should try cleaning your solution.

blocks|key|930272|text|发布我的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|930273|该问题与Mcafee+Antivirus的“访问扫描”有关。禁用此功能解决了问题。不知何故，当杀毒软件打开时，ASP没有正确使用ASP临时文件夹。|930274|希望这对某些人有帮助。|930275|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Posting my solution: 

The issue was related to the "On-Access Scan" of Mcafee Antivirus. Disabling this solved the problem. Somehow, the ASP Temporary folder was not being used properly by ASP when the antivirus was ON.

Hope this helps someone.

blocks|key|126722|text|为了防止其他人也遇到我的问题，我在尝试发布新分支项目的Web站点时遇到了这个错误，build+worked。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126723|原来我忘了去掉发布设置下的“Allow预编译站点可更新”复选框->+Configure预编译。|offset|length|style|BOLD|126724|entityMap^0|0|7|4|D|X|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

Just in case someone else shares my problem, I got this error when trying to publish a Web Site of a newly branched project, build worked perfectly.

Turns out I had forgotten to remove the checkbox for "Allow precompiled site to be updatable" under publish Settings -> Configure precompile.

blocks|key|4190132|text|这些解决方案对我都不起作用。我的两个冲突的ASP.NET都在C:...\AppData...\Temporary+DLLs+...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4190133|问题是，在我们将一个类型从一个项目移动到同一解决方案中的另一个项目之前，我已经将我的源代码库回滚到了一个较早的版本。|4190134|我试着从msbuild指定的“临时ASP.NET文件”位置删除新的动态链接库--它根本不应该出现在旧的代码库中。msbuild把它放回去就行了。|4190135|我还尝试了web.config设置，这里的一些人已经成功地使用了该设置，但也不起作用。虽然，在我写这篇文章的时候，我意识到在同一个解决方案中实际上有两个MVC项目，并且都有错误，所以问题可能是我没有将设置都添加到这两个项目中。|4190136|我试着前滚我的源代码库，清理，然后再回滚，再清理。没什么。|4190137|我尝试删除“临时ASP.NET文件”位置的所有内容。msbuild只是把它放回原处。|4190138|最后，我尝试在Visual+Studio中进行重新构建。尽管命令行输出和"Errors“输出都给出了相同的msbuild+"Temporary+ASP.NET+Files”错误，但当鼠标悬停在冲突的类型上时，智能感知错误实际上抱怨输出目录中的DLL。显然，“清理”和“重建”没有做好他们的工作。我手动删除了由Intellisense标识的输出目录中的DLL，问题就解决了。|4190139|tl;dr+-确保你使用批处理设置覆盖了所有的web.configs，并尝试利用智能感知来获得进一步的线索。|4190140|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

None of these solutions worked for me. Both of my conflicting DLLs were in C:\...\AppData\...\Temporary ASP.NET Files\...

The problem was that I had rolled back my source repo to an earlier version - before we moved a type from one project to another project within the same solution.

I tried deleting the newer DLL - which should not have even been there at all in the older codebase - from the "Temporary ASP.NET Files" location identified by msbuild. msbuild just put it back.

I also tried the web.config setting that some here have used successfully, but that did not work either. Although, as I write this, I realize that there were actually two MVC projects within the same solution and both had errors, so the problem may have been that I did not add the setting to both.

I tried rolling my source repo forward and cleaning and rolling back again and cleaning. Nothing.

I tried deleting everything the "Temporary ASP.NET Files" location. msbuild just put it back again.

Finally, I tried rebuilding in Visual Studio. Although the command line output and the "Errors" output both gave the same msbuild "Temporary ASP.NET Files" error, the Intellisense error - when hovering over the conflicted type - actually complained about DLLs in output directories. Apparently "Clean" and "Rebuild" were not doing their jobs. I manually deleted the DLLs in the output directories identified by Intellisense, and the problem was solved.

tl;dr - Make sure you're covering all of your web.configs with the batch setting, and try to leverage Intellisense for further clues.

blocks|key|4190170|text|我的问题链接到在我的项目文件夹中生成的.dll。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4190171|如果您正在引用另一个文件，而不是执行上面看到的所有操作，那么立即解决我的问题的方法就是删除我的项目的/bin目录中的.dll。|4190172|这个问题不一定是web.config修复--它是一个需要解决的循环引用。我意识到我在原始项目文件中清除了旧的.dll，而不是在引用它的项目中。|4190173|我不建议对您的web.config文件进行修改，因为这只是一个权宜之计-并没有真正解决实际问题。如果你不想修复这个问题，可以这样做，但是如果你想避免将来的麻烦，只需从这两个地方删除.dll即可。|4190174|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

My problem was linked to a .dll that was getting generated in my project folder. 

If you are referencing another file, instead of doing everything you see above, what fixed my problem instantly was just deleting the .dll that was staying inside my /bin directory for my project. 

The problem isn't necessarily a web.config fix - it's a circular reference that needs to get resolved. I realized that I cleared the old .dll in my original project file but not in the project that was referencing it. 

I don't recommend making the modification to your web.config file because that's just a band-aid fix - not really addressing the actual problem. Do that if you don't feel like fixing the problem, but if you want to avoid future headaches, just remove the .dll from both places.

blocks|key|126854|text|App_Code文件夹导致了问题，请将类放在该文件夹之外(工作正常)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|126855|App_Code文件夹不是为网站应用程序项目设计的|126856|http://vishaljoshi.blogspot.in/2009/07/appcode-folder-doesnt-work-with-web.html|offset|length|126857|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|27|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

App_Code folder is causing the problem , put the class outside the folder (Works fine)

App_Code folder is not designed for Web Application Projects 

<a href="http://vishaljoshi.blogspot.in/2009/07/appcode-folder-doesnt-work-with-web.html" rel="nofollow">http://vishaljoshi.blogspot.in/2009/07/appcode-folder-doesnt-work-with-web.html</a>

blocks|key|925656|text|转到添加引用并搜索两个dll，这两个dll都会被选中，取消选中其中一个dll，因为有不同版本的引用会生成相同的dll。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|925657|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Go to Add reference and search for both the dll,
Both of the dll would have checked, uncheck one of the dll, as there are references to the same dll with different version ambiguity gets generated.

blocks|key|4190298|text|我的解决方案是替换CodePage="....“使用CodeBehind="...“在.aspx文件中。不知怎么的，在从以前的.NET版本迁移的过程中，它被保留为CodePage。此页指令创建了另一个与项目dll文件冲突的dll文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4190299|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My solution was to replace CodePage="...." with CodeBehind="..." in the .aspx file. Somehow it was left as CodePage during a migration from previous .NET versions.
This page directive creates another dll file which conflicts with the projects dll file.

blocks|key|4190315|text|我在两个不同的项目中有一个同名的分部类。我只把它放在一个项目中就解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4190316|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a partial class with the same name in two different projects.
I solved it by only leaving it in one project.

blocks|key|925681|text|这些解决方案对我都不起作用。在“发布”模式下编译是有效的，但是当我切换到“调试”模式时，我得到了许多这样的错误信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|925682|我不明白为什么，但我的解决方案是对Visual+Studio进行简单的重启。|offset|length|style|BOLD|925683|entityMap^0|0|Z|3|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

None of this solutions worked for me. Compiling in "Release" mode worked, but when I switched to "Debug" I got umpteen of this error Messages.

I don't understand why, but a simple restart of Visual Studio was my solution.

When running a web application project, at seemingly random times a page may fail with a CS0433 error: type exists in multiple DLL's. The DLL's are all generated DLL's residing in the "Temporary ASP.NET Files" directory.

ASP.Net error: "The type 'foo' exists in both "temp1.dll" and "temp2.dll"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在运行ASP.NET应用程序项目时，页面可能会随机出现错误:类型存在于多个动态链接库中。这些动态链接库都是位于"Temporary web Files“目录中的所有生成的动态链接库。

问ASP.Net错误：“类型'foo‘存在于"temp1.dll”和"temp2.dll“中”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.Net错误：“类型'foo‘存在于"temp1.dll”和"temp2.dll“中”EN