服务器返回一个asp.net 3.5 IIS6上的空白页服务器、空白页、asp、net
我有一个网站部署在IIS6断绝了问题。这里的问题，当我第一次部署asp.net 3.5网站服务器（网站是比较小的5页和5图书馆仓），它是按预期工作。但一段时间后（〜1H）服务器返回的黑色页面，而不是预期的内容：
I have a problem with site deployed on IIS6 sever. Here the problem, when I first deploy asp.net 3.5 site to server (site is relatively small with 5 pages and 5 libraries in bin), it is works as expected. But after some period of time (~1h) server returns black pages instead of expected content:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8"></HEAD>
<BODY></BODY></HTML>
首先我的想法是，我与其他.NET 2.0网站托管在同一服务器中，所以我把我的网站进入专用游泳池，但没有成功网站的冲突。第一次现场工作，那么没有。没有任何错误或像在IIS日志的东西。而且我也不在我的网站上使用ClearError（）方法。
First my idea was that my site conflicts with other .net 2.0 sites that hosted in the same server, so I put my site into dedicated pool but without success. First time site works, then no. There is no errors or something like that in iis logs. And I do not use ClearError() method in my site.
我已经发现了类似的问题，here （我得到使用传统的ASP，IIS6和WinServer 2003 R2中的空白页，而不是错误消息），但它是传统的ASP。
I have found similar question here (I’m getting blank pages instead of error messages using classic ASP, IIS6 and WinServer 2003 R2), but it is for classic ASP.
另外几个主题，在ASP.NET：
Also several topics at ASP.NET:
空白页的问题。 上部署网站时出现空白页 在IIS 7中 空白页的服务器2K8 Blank page problem. Blank pages on deployed website blank page in IIS 7 on Server 2K8但这个解决方案还不能帮我。例如，当我更换web.config文件与新的，或者更换所需组件与rebuilded的一个，我也有同样的结果。第一次现场工作，然后 - 黑页
But this solutions also not help me. For example when I replace web.config with new one, or replace one of the required assemblies with rebuilded one, I have the same result. First time site works, then - black pages.
这是我所看到的，我认为这是种配置问题，但我完全惊呆了，现在，因为我已经尝试了一切，现在我没有任何想法，所以帮助非常AP preciated。
From what I see, I think that this is kind of configuration problem, but I completely stunned right now, because I've tried everything and now I lack any ideas, so help is very appreciated.
推荐答案
我没有找到问题的根源。但问题是使用发布Project向导解决。原变种被分布在xcopy的基础上与code-背后的来源。
I didn't find the origins of the problem. However problem was solved by using Publish Project wizard. Original variant was distributed at xcopy basis with code-behind sources.
