每当我使用Framework 2.0代码时，VS 2008的构建失败 [英] Build Fails for VS 2008 whenever i am using Framework 2.0 Code

问题描述

我使用了来自WROX的IMAR Spa ....的"ASP.NET 2.0即时结果"中的代码，并使用VS 2005修改了代码，然后构建它对我来说非常好，但最近受到了攻击文件夹病毒.

因此，我要删除VS 2005并同时升级系统.后来，我安装了VS 2008，并将整个代码从VS 2005代码库复制到VS 2008 Project中，并根据我的需要修改了代码并发布了.

但是根据要求，本月早些时候(2011年10月1日)，我从Microsoft升级了带有SP1版本的My VS 2008，因为那时我遇到了构建失败错误，也无法跟踪其中的任何错误.为了删除这个，我再次删除了整个Windows安装并继续使用初始IDE，但是仍然出现相同的错误.

您能否告诉我，以前在Windows上带有SP1的窗口中的最后一次发布是否已写入我的设置"文件中，或者我的代码是否进行了其他任何更改，从而导致构建失败而没有任何错误.因为我一直使用相同的代码来构建.

我无法还原更改，因为我的代码包含1200多个文件夹和100000个文件，并且大小超过300 MB.我在我的网站中使用过Jquery，Javascript，Vb.net文件，cs.net文件，Sitemap，DB's等.

请任何人帮我调试和发布我的网站.

谢谢DS

I used a code from ''instant results for ASP.NET 2.0'' from IMAR Spa.... of WROX and modified the code using VS 2005 and then build it was very good for me but recently got the attack of folder virus.

So I was to remove my VS 2005 and Upgraded the system as well. Later on I installed VS 2008 and copied whole of the code in to a VS 2008 Project from VS 2005 code base and modified the code as per my needs and published as well.

But as per the requirements Earlier this month on 1 OCT 2011, I upgraded My VS 2008 with SP1 build from Microsoft since then i am getting build failed error and also no able to trace any errors in it. To remove this i again removed whole of the windows Installation and get on with initial IDE but still I am getting the same error.

Could you please tell me if the last publish on previous windows with SP1 had wrote in my Settings files or did any others changes in my code which is causing build failed with out any errors. because i have used the same code always to build.

I cannot revert the changes as my code contains more then 1200 folders and more then 100000 files and is more then 300 MB in size. i have used Jquery, Javascript, Vb.net files, cs.net files, Sitemaps, DB''s, etc in my website.

Please could any one help me debugging and publishing my website.

Thanks DS

推荐答案

与此问题相关的几种可能结果，可以在下面的查找问题原因并解决错误"中给出.

0.
您可以在输出"窗口中查找.如果没有提供足够的细节，
您可以使用工具"->选项"->项目"和
来更改详细程度 解决方案-& gt;生成并运行:MSBuild项目生成输出详细信息.

1.
您是否曾经让Visual Studio告诉过您您的Web应用程序发布失败，但是却从未给出原因?你不是一个人.我一直在推迟在一个项目上研究这个问题，并找到了一种方法来立即获得我的答案. Visual Studio 2008的发布失败"消息.
这是您在Visual Studio内部应该执行的操作，以找出发布失败的原因. 1.点击工具"菜单& gt;然后单击选项"以显示选项"对话框.
2.展开左侧的项目和解决方案"，然后点击常规
3.在常规"上，单击构建开始时显示输出窗口"
4.现在，单击左侧树中的构建并运行"
5.接下来，从"MSBuild项目构建输出详细程度"下拉菜单中选择一个值
6.确定返回Visual Studio主窗口的方法
7.下次生成或发布项目时，应该会看到输出"面板弹出.如果您的发布仍然失败，答案将保留在输出"面板中

2.
工具& gt;选项& gt;项目与解决方案一般
工具& gt;选项& gt;项目与解决方案生成并运行
Visual Studio的输出面板

3.
您需要查询输出"窗口以获取更多信息.
查看& gt;输出
或
< code> Ctrl + Alt + O</code>

4.

如果我们创建一个简单的ASP.NET网站并使用VS 2008进行发布，是否会遇到相同的问题?如果您使用的是Vista或Win 7，请尝试以管理员身份运行VS 2008.若要解决此问题，您还可以将"MSBuild项目的生成输出详细程度"选项从(工具"菜单，单击选项"，然后选择"Projects and Solutions"文件夹，然后单击生成并运行")更改为
获取详细的构建步骤.

5.
MSBuild可以很好地报告构建错误，但是MSBuild只能报告错误
基础任务报告.自定义任务为
的质量增加了很多变化 错误消息.例如，以下消息作为截止日期弹出
隐约可见.
构建失败.
0警告
0个错误
时间已过00:00:05.85
构建失败，但是没有错误要报告.是的.像这样奇怪的消息
那让我想用德语骂人，但我不懂德语，所以我大声喧<
在柏林住了5年后可能会生气的克林贡.
在将MSBuild设置为最大详细程度之前，我无法在输出中发现任何问题
(/verbosity:diagnostic，简称/v:diag)，这时我在输出中发现了这一点:
在项目"..."中完成了构建目标"PrepareRdlFiles".
在文件"..."中定位目标"RunRdlCompiler":
完全构建目标"RunRdlCompiler".
输出文件"obj \ Debug \ RdlCompile.compiled"不存在.
使用程序集"Microsoft.ReportViewer.Common ..."中的"RdlCompile"任务.
任务"RdlCompile"
完成执行任务"RdlCompile"-失败.
在项目"CareAlertsWeb.csproj"中完成构建目标"RunRdlCompiler"-失败.
有人已将.rdlc文件添加到项目中.这些是客户报告定义"文件-
考虑没有报表服务器的Reporting Services报表.出问题了
编译.rdlc文件，但仍然没有任何信息可以确定
问题是.在不知道还要做些什么的情况下，我开始查看RdlCompile任务
使用Reflector.
RdlCompile任务很有趣.该任务不会按照传统意义编译文件
(将输入转换为输出).该任务将验证.rdlc
中的报告定义 文件.此步骤可确保我们从
获取编译时错误，而不是运行时错误 如果报表定义无效，则使用ReportViewer控件.
托管RdlCompile的程序集引用了另一个不在构建中的程序集
计算机(Microsoft.ReportViewer.ProcessingObjectModel).神秘.为什么会造成这种情况
在没有报告更具体错误的情况下失败的任务也是一个谜.
在所有程序集均安装到位后，RdlCompile任务成功完成.跑步
ReportViewer.exe将安装所有必需的程序集，您可以在％Program
中找到它. Files％\ Microsoft Visual Studio 8 \ SDK \ v2.0 \ BootStrapper \ Packages \ ReportViewer.

6.
如果选择此选项，则标记保持原样，允许您在预编译网站后更改HTML和客户端功能.选择此选项等效于将-u选项添加到aspnet_compiler.exe命令.有关更多信息，请参见使用可更新的UI和ASP.NET编译工具进行预编译以进行部署(Aspnet_compiler.exe).

一个).如果希望能够通过重新编译来更新各个页面，请选择使用固定命名和单页面程序集".此选项可能会降低大型站点的性能.有关更多信息，请参见以下
主题:
预编译为固定名称程序集
ASP.NET编译工具(Aspnet_compiler.exe).
如何:使用ASP.NET编译工具生成固定名称
b).如果希望能够在已发布的网站上进行调试，请选择发出调试信息".
C).要使用密钥文件或密钥容器创建强命名的程序集，请选择启用强"
在预编译的程序集上命名复选框，选择相应的单选按钮，然后输入
适当的信息密钥文件位置或密钥容器框.
强名称程序集可以部署到服务器的全局程序集缓存(GAC)或Bin
应用程序的目录.签名的程序集使恶意用户更难替换
应用程序的程序集带有恶意代码.但是，共享中密钥管理的复杂性
开发环境可能胜过签名程序集的优点.有关
的信息 关于程序集的强命名，请参阅以下主题:
预编译为已签名的程序集
ASP.NET编译工具(Aspnet_compiler.exe)
如何:为预编译的网站项目签名程序集
d).如果选择在预编译的程序集上启用强命名"，并且使用密钥文件，并且如果
您要延迟对密钥文件的签名，请选择延迟签名".
如果选择此选项，则将在两个阶段对程序集进行签名:首先使用公钥文件，然后使用
稍后在调用aspnet_compiler.exe命令期间指定的私钥文件.
e).如果选择在预编译的程序集上启用强命名"，并且要允许
要通过部分受信任的代码调用的程序集，请选择将程序集标记为
AllowPartiallyTrustedCallerAttribute(APTCA).
程序集必须具有由ASP.NET调用的AllowPartiallyTrustedC allersAttribute属性. 运行.有关更多信息，请参见AllowPartiallyTrustedC allersAttribute.
F).单击确定.
发布状态显示在任务栏中.发布完成后，发布状态为
显示成功.

7.
最后的答案是，这是一个已知的错误:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=317870
答案是将包含LINQ的项目文件(* .csproj)修改为SQL dbml文件，以删除某些内容，例如
如下:
一个.关闭VS2008.
b.在记事本中打开包含LINQ To SQL项的项目文件.
C.删除以下行:
[ItemGroup]
[Service Include ="{3259AA49-8AA1-44D3-9025-A0B520596A8C}"/]
[/ItemGroup]
现在，安装项目将成功构建.但是，如果双击DBML文件以在VS 2008中打开设计器，则安装项目将再次停止构建.上面的行不会重新添加到项目文件中，但是无论如何安装项目都会停止构建.只需重新启动VS 2008，它就会再次起作用-直到再次打开DBML设计器为止.一旦安装程序项目由于此问题而失败，则在重新启动VS 2008之后，它将永远无法成功构建.

8.
列出的另一个解决方法是可行的:右键单击解决方案，然后在Visual Studio中单击清理解决方案"

9.
您可以在VS中编辑csproj文件而无需关闭解决方案:1.从项目上下文菜单中卸载项目，2.从上下文菜单中，在VS中打开csproj文件，3.编辑&保存，4.从上下文菜单中重新打开项目

10.
首先，右键单击您的解决方案文件& gt;属性& gt;配置
在其中，使用构建复选框来试验哪些项目可以一起构建，哪些不可以.另外，在文件系统中，删除所有项目的调试/发布文件夹.
最后，以我的经验，此错误通常是由于web.config损坏/丢失引起的.
11.
有时，如果您追踪build命令(在输出中，它会得到更好的错误消息
Windows)，看起来像
E:\ Windows \ Microsoft.NET \ Framework \ v3.5 \ Csc.exe/noconfig/nowarn:1701,1702/errorrep...blah..blah
然后在命令行上手动运行它.另外，即使Visual Studio的默认行为是在构建失败后显示错误列表"窗口，输出窗口也往往具有更好的信息.

12.
当您说清洁时，您的意思是右键单击解决方案，然后单击清洁解决方案?
您是否尝试过手动从Bin文件夹中删除所有内置的dll，并确保没有其他正在运行的应用程序打开文件.不确定VS是否存在问题，但不确定文件或文件夹以."开头.会引起问题.例如，如果未将SubVersion设置为使用"_svn"而不是".svn"

13.
尝试将项目根目录移动到驱动器的根目录.我遇到了一个非常大的项目的问题，该项目的路径长度太长，开始引起问题.
因此，而不是:
c:\我的文档和设置\<用户名> \我的文档\ Visual Studio 2008 \ Projects \<项目名称> \ PrecompiledWeb \<项目名称> \ .. \ .. \ .. \ ... \\ abc .xyz
为此:c:\ Visual Studio 2008 \ Projects \< project_name> \ .. \ .. \ .. \ .. \ .. \ abc.xyz
这里< user_name>描述系统用户的名称，< project_name>项目名称和\ .. \ .. \ .. \ .. \ .. \ abc.xyz描述项目内部由用户创建的文件和文件夹.或者可以简化为c:\ Publish \< project_name> \ .. \ .. \ .. \ .. \ .. \ abc.xyz或c:\< project_name> \ .. \ .. \ .. \ .. \ .. \ abc.xyz

14.
在最后但并非最不重要的一点上，我必须说:-
http://connect.microsoft.com/VisualStudio/feedback/details/345523/2008-web-deployment-projects-wdp-fail-build-without-error-when-the-visual-studio-2008-sdk-is-已安装

这与发布在< a href ="http://blogs.msdn.com/webdevtools/archive/2008/01/25/announcing-rtw-of-visual上的Visual Studio 2008 Web部署项目(WDP)有关-studio-2008-web-deployment-projects-wdp.aspx> http://blogs.msdn.com/webdevtools/archive/2008/01/25/announcing-rtw-of-visual-studio-2008-web -deployment-projects-wdp.aspx</a>
以及发布在< a href ="http://www.microsoft.com/downloads/details.aspx?familyid=30402623-93ca-479a-867c-04dc45164f5b&displaylang=zh-CN"上的Visual Studio 2008 SDK ; http://www.microsoft.com/downloads/details.aspx?familyid = 30402623-93ca-479a-867c-04dc45164f5b& displaylang = zh-CN/a (来自http://msdn.microsoft.com/zh-cn/vsx/).

如果安装了2008 Web Deployment Projects，但未安装Visual Studio 2008 SDK，则Web Deployment Projects将成功构建.
如果同时安装了2008 Web Deployment Projects和Visual Studio 2008 SDK，则Web Deployment Project生成将失败，但不会出现错误消息.
如果卸载了Visual Studio 2008 SDK，并且未修改2008 Web Deployment Projects的安装，则Web Deployment Projects将再次成功构建.
重要的是要注意，解决方案中的任何代码(包括Web应用程序项目和Web部署项目)都不会尝试以任何方式使用Visual Studio 2008 SDK. VS 2008 SDK仅存在于系统上似乎破坏了Web部署项目的构建过程，即使对于基本的"Hello World" Web应用程序也是如此.
附加了两个文件-
*日志-这是安装Visual Studio 2008 SDK时进行构建尝试的日志文件，日志级别设置为诊断"
* Zip-这是一个非常基本的解决方案，包含一个"Hello World" Web应用程序项目和一个相应的Web部署项目.如果安装了Visual Studio 2008 SDK，则此Web部署项目将无法生成，但不会出现任何错误.如果未安装Visual Studio SDK，则整个解决方案将成功构建. ;</user_name>

There are several possible results related to this issue and can be given here in as Follows find your Cause and resolve the bug.

0.
You can look in the Output window. If that doesn''t provide enough detail,
you can change the level of detail with Tools-&gt;Options-&gt;Projects and
Solutions-&gt;Build and Run: MSBuild project build output verbosity.

1.
Have you ever had Visual Studio tell you your web application publish failed, but never gives you a reason why? You’re not alone. I’ve been putting off looking into this issue on a project and just found a way to get my answer right away. Visual Studio 2008''s Publish Failed message.
Here’s what you should do inside of Visual Studio to find out why your publish failed.
1. Click the Tools menu &gt; then Options to bring up the Options dialog.
2. Expand ‘Projects and Solutions’ on the left and click General
3. On General, click ‘Show Output window when build starts’
4. Now click on ‘Build and Run’ in the left tree
5. Next select a value from the ‘MSBuild project build output verbosity’ drop down menu
6. OK your way back to the main Visual Studio window
7. The next time you Build or Publish your project, you should see the Output panel pop up. If your publish is still failing, the answer will live inside the Output panel

2.
Tools &gt; Options &gt; Projects and Solutions &gt; General
Tools &gt; Options &gt; Projects and Solutions &gt; Build and Run
Visual Studio''s Output Panel

3.
You need to consult the Output window for more information.
View &gt; Output
or
<code>Ctrl+Alt+O</code>

4.
Hi,
If we create a simple ASP.NET website and publish it using your VS 2008, does it have the same issue? If you are using Vista or Win 7, please try to run VS 2008 as Administrator. To troubleshoot the issue, you also can change "MSBuild project build output verbosity" option from (Tools menu, click Options, and then select the Projects and Solutions folder and click Build and Run) to
get detailed build steps.

5.
MSBuild does a good job of reporting build errors, but MSBuild can only report errors
that the underlying Tasks report. Custom tasks add a lot of variation to quality of the
error messages. Case in point is the following message, which popped up as a deadline
loomed.
Build FAILED.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:05.85
The build failed, but there are no errors to report. Yup. It''s strange messages like this
that make me want to curse in German, but I don''t know German, so I make the noises an
angry Klingon might make after living in Berlin for 5 years.
I couldn''t find any problems in the output until I set MSBuild for maximum verbosity
(/verbosity:diagnostic, /v:diag for short), at which point I found this in the output:
Done building target "PrepareRdlFiles" in project "...".
Target "RunRdlCompiler" in file "...":
Building target "RunRdlCompiler" completely.
Output file "obj\Debug\RdlCompile.compiled" does not exist.
Using "RdlCompile" task from assembly "Microsoft.ReportViewer.Common ...".
Task "RdlCompile"
Done executing task "RdlCompile" -- FAILED.
Done building target "RunRdlCompiler" in project "CareAlertsWeb.csproj" -- FAILED.
Someone had added .rdlc files to the project. These are "Client Report Definition" files -
think of Reporting Services reports without a report server. Something was going wrong
compiling the .rdlc files, but there still wasn''t any information to determine what the
problem was. Without knowing what else to do I started looking at the RdlCompile task
with Reflector.
The RdlCompile task is interesting. The task doesn''t compile files in the traditional sense
(transform inputs into outputs). The task validates the report definition inside the .rdlc
file. This step ensures we''ll get compile time errors instead of runtime errors from the
ReportViewer control if the report definition is invalid.
The assembly hosting RdlCompile referenced another assembly that was not on the build
machine (Microsoft.ReportViewer.ProcessingObjectModel). Mysterious. Why this caused
the task to fail without reporting a more specific error is also a mystery.
With all the assemblies were in place, the RdlCompile task finished with success. Running
ReportViewer.exe installs all the required assemblies, you can find it in %Program
Files%\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\ReportViewer.

6.
If you select this option, the markup is left as-is, allowing you to change HTML and client-side functionality after precompiling the Web site. Selecting this option is equivalent to adding the -u option to the aspnet_compiler.exe command. For more information, see Precompiling for Deployment with Updatable UI and ASP.NET C ompilation Tool (Aspnet_compiler.exe).

a). If you want to be able to update individual pages by recompiling them, select Use fixed naming and single page assemblies. This option might degrade the performance of a very large site. For more information, see the following
topics:
Precompiling to Fixed-Name Assemblies
ASP.NET C ompilation Tool (Aspnet_compiler.exe).
How to: Generate Fixed Names with the ASP.NET C ompilation Tool
b). If you want to be able to debug in the published Web site, select Emit debug information.
c). To create strongly named assemblies using a key file or a key container, select the Enable strong
naming on precompiled assemblies check box, select the appropriate radio button, and enter the
appropriate information Key file location or Key container box.
Strong-named assemblies can be deployed to the server''s global assembly cache (GAC ) or to the Bin
directory of the application. A signed assembly makes it more difficult for malicious users to replace the
application''s assemblies with malicious code. However, the complexity of key management in shared
development environments might outweigh the advantages of signed assemblies. For information about
strong-naming on assemblies, see the following topics:
Precompiling to Signed Assemblies
ASP.NET C ompilation Tool (Aspnet_compiler.exe)
How to: Sign Assemblies for Precompiled Web Site Projects
d). If you select Enable strong naming on precompiled assemblies, and if you use a key file, and if
you want to delay the signing of the key file, select Delay signing.
If you select this option, the assembly is signed in two stages: first with the public key file, and then with
a private key file that is specified later during a call to the aspnet_compiler.exe command.
e). If you selected Enable strong naming on precompiled assemblies, and if you want to allow the
assemblies to be called by partially trusted code, select Mark assemblies with
AllowPartiallyTrustedCallerAttribute (APTCA).
Assemblies must have the AllowPartiallyTrustedC allersAttribute attribute to be called by the ASP.NET
runtime. For more information, see AllowPartiallyTrustedC allersAttribute.
f). C lick OK.
Publishing status is displayed in the taskbar. When publishing is completed, the status of Publish
succeeded is displayed.

7.
The answer in the end was that it is a known bug:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=317870
The answer is to modify project files (*.csproj) containing LINQ to SQL dbml files to remove some stuff, as
follows:
a. Close VS 2008.
b. Open the project file containing the LINQ To SQL item in Notepad.
c. Remove the following lines:
[ItemGroup]
[Service Include="{3259AA49-8AA1-44D3-9025-A0B520596A8C}"/]
[/ItemGroup]
The Setup Project will now build successfully. However, if you double-click the DBML file to open the designer in VS 2008 the Setup Project will stop building again. The above lines do not get re-added to the project file but the Setup Project will stop building anyway. Just restart VS 2008 and it will work again -- until you open the DBML designer again. Once the Setup Project fails due to this problem it will never build successfully until after you restart VS 2008.

8.
Another workaround listed worked : right click on the solution and click "Clean Solution" in Visual Studio

9.
You can edit a csproj file in VS without closing the solution: 1. from the project context menu unload the project, 2. from the context menu open the csproj file in VS, 3. edit & save, 4. from the context menu re-open the project

10.
Firstly, right-click on your Solution file &gt; Properties &gt; Configuration
In there, use the build tick boxes to experiment with which projects build together, and which don''t. Also, in your file system, delete the debug/release folders for all of your projects.
Finally, in my experience, this error is usually caused by a corrupt/missing web.config

11.
Sometimes you get better error messages if you track down the build command (its in the output
windows) and looks like
E:\Windows\Microsoft.NET\Framework\v3.5\Csc.exe /noconfig /nowarn:1701,1702 /errorrep...blah..blah
Then run that manually at the command line. Also, the output window tends to have better information, even though Visual Studios default behavior is to show the "Errors List" window after a failed build.

12.
When you say cleaning, you mean Right Clicking on the Solutions and clicking Clean Solutions?
Have you tried removing all the built dlls from the Bin folder manually and making sure no other running applications have files open. Not sure if its sill an issue with VS, but files or folders starting with a "." can cause problems. eg if SubVersion is not set to use "_svn" instead of ".svn"

13.
Try moving the project root the root of the drive. I had run into an issue with a very large project where the path length was so long it had started to cause issues.
So rather than:
c:\My Documents and Settings\<user_name>\My Documents\Visual Studio 2008\Projects\<project_name>\PrecompiledWeb\<project_name>\..\..\..\..\..\abc.xyz
do this: c:\Visual Studio 2008\Projects\<project_name>\..\..\..\..\..\abc.xyz
here <user_name> Describes the name of the system User, <project_name> Project name and \..\..\..\..\..\abc.xyz Describes files and folders inside the project which was created by user. Or can reduce to c:\Publish\<project_name>\..\..\..\..\..\abc.xyz or to c:\<project_name>\..\..\..\..\..\abc.xyz

14.
and in the last but not the least I must say :-
http://connect.microsoft.com/VisualStudio/feedback/details/345523/2008-web-deployment-projects-wdp-fail-build-without-error-when-the-visual-studio-2008-sdk-is-installed

This is related to the Visual Studio 2008 Web Deployment Projects (WDP) as posted on <a href="http://blogs.msdn.com/webdevtools/archive/2008/01/25/announcing-rtw-of-visual-studio-2008-web-deployment-projects-wdp.aspx">http://blogs.msdn.com/webdevtools/archive/2008/01/25/announcing-rtw-of-visual-studio-2008-web-deployment-projects-wdp.aspx</a>
as well as the Visual Studio 2008 SDK as posted on <a href="http://www.microsoft.com/downloads/details.aspx?familyid=30402623-93ca-479a-867c-04dc45164f5b&displaylang=en">http://www.microsoft.com/downloads/details.aspx?familyid=30402623-93ca-479a-867c-04dc45164f5b&displaylang=en</a> (from http://msdn.microsoft.com/en-us/vsx/ ).

If 2008 Web Deployment Projects is installed and the Visual Studio 2008 SDK is NOT installed, Web Deployment Projects will build successfully.
If both 2008 Web Deployment Projects and the Visual Studio 2008 SDK are installed, Web Deployment Project builds will fail, but there will be no error messages.
If the Visual Studio 2008 SDK is uninstalled and the 2008 Web Deployment Projects installation is left unmodified, Web Deployment Projects will again build successfully.
It is important to note that no code in the solution (including both the Web Application Project and the Web Deployment Project) attempts to use the Visual Studio 2008 SDK in any way. The mere presence of the VS 2008 SDK on the system seems to corrupt the build process for Web Deployment Projects, even for a basic "Hello World" web application.
Two files are attached--
* Log - This is a log file of a Build attempt while the Visual Studio 2008 SDK is installed, with the log level set to "Diagnostic"
* Zip - This is a very basic solution that contains a "Hello World" Web Application Project and a corresponding Web Deployment Project. If the Visual Studio 2008 SDK is installed, this Web Deployment Project will fail to build, but there will be no errors. If the Visual Studio SDK is NOT installed, the entire solution will build successfully.</project_name></project_name></project_name></user_name></project_name></project_name></project_name></user_name>

这篇关于每当我使用Framework 2.0代码时，VS 2008的构建失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！