编译问题，或者是吗？ [英] Compiling problem, or is it?

问题描述

我有一个由9个项目组成的解决方案，每个项目都有不同的引用，每个

其他（干净，没有循环等）。 Visual Studio有时会给我

奇怪的错误，它找不到一个引用的程序集，不能

写一个，或者现在最常见的（几乎100个） ％的时间）：失败

在尝试启动编译时发生。


但实际上编译似乎已成功完成。我已经获得了一个新创建的exe并且运行得很好，即使在Visual Studio中来自

的调试模式下也是如此。


之前错误导致我看到这篇知识库文章，但是虽然症状

相似但我已经检查了所有内容并且它似乎并不适用。 （一个

的程序集是96k编译的。）
http://support.microsoft.com/default...b;en-us;313512


我以前也有这个问题。它似乎现在已经解决了，但也许是b $ b仍然以某种方式相关：
http://support.microsoft.com/default...b;en-us;825007


现在这主要是一个大型的新生，因为一切都通常很好

尽管有消息。有时我必须退出并重新加载VS才能获得它再次编译
，这真的很烦人。


有什么建议吗？

解决方案

更正：


当我进行重建解决方案时，其中一个程序集不会重建。


我从该项目的obj和

bin文件夹的调试子文件夹中删除了.dll文件。当我重新启动VS时，我当然收到了一些消息，说明它无法找到装配/依赖。重建解决方案了吗？所有的东西

似乎已编译，但VS仍然告诉我它无法找到程序集。


退出并重新启动VS并且消息消失了。重建解决方案，我是
回到失败状态在同一个程序集上的消息，它是唯一没有重新编译的

程序集。


无论它的价值如何，导致问题的装配不是96k

装配，而是仅由96k装配引用。 96k组件也是b $ b引用其他人。


Daniel Billingsley < dbillingsley@NO_durcon_SPAAMM.com>在消息中写道

新闻：e9 ************** @ TK2MSFTNGP14.phx.gbl ...

我有一个解决方案，包括9个项目，每个项目都有各自的参考（干净但没有循环等）。 Visual Studio有时会给我一些奇怪的错误，它找不到一个引用的程序集，不能写一个，或者现在最常写（几乎100％的时间）：尝试启动编译时发生了故障。

但实际上编译似乎已成功完成。我已经获得了一个新创建的exe，它运行得很好，即使在Visual Studio中的调试模式下也是如此。

在错误导致我进入这个KB之前文章，但虽然
症状是相似的，我已经检查了所有的东西，似乎并没有适用。
（其中一个程序集是96k编译的。）
http://support.microsoft.com/default...b;en-us;313512

我以前也遇到过这个问题。它似乎现在已经解决了，但也许
仍然有点相关：
http://support.microsoft.com/default...b;en-us;825007

现在这主要是一个大的新生，因为尽管有这样的信息，一切都很好。
有时候我必须退出并重新加载VS才能再次编译它，这真的很烦人。

有什么建议吗？

我假设你已经检查了你的构建订单，对吧？


我认为没有任何完全治愈的方法问题（但是如果有人知道更好的话，我将会看到
。）然而，当我无法重建时，有时我发现

;，我可以建立。然后我通常会离开VS然后再回来。（不是说我有理由这样做，它更像是一个

宗教仪式，我每当我的构建过程需要时，就会执行

清理。之后，重建通常似乎有效。


希望这有助于......

-Rachel


" Daniel Billingsley" < dbillingsley@NO_durcon_SPAAMM.com>在消息中写道

news：uH ************** @ TK2MSFTNGP10.phx.gbl ...

更正：

当我进行重建解决方案时，其中一个程序集没有重建。

我删除了该项目的obj和
bin的调试子文件夹中的.dll文件文件夹。当我重新启动VS时，我当然得到了一些消息，说明它无法找到程序集/依赖。重建解决方案。
一切似乎已编译完成，但VS仍告诉我它无法找到
程序集。

已退出并重新启动VS和消息消失了。重建解决方案，我又回到了失败状态。在同一个程序集上的消息，它是唯一没有重新编译的程序集。

无论它的价值如何，导致问题的程序集都不是96k
装配，但仅由96k一个参考。 96k组件也引用了其他人。

Daniel Billingsley < dbillingsley@NO_durcon_SPAAMM.com>在消息中写道
新闻：e9 ************** @ TK2MSFTNGP14.phx.gbl ...

我有一个由9个项目组成的解决方案各种各样的参考
其他（干净但没有循环等）。 Visual Studio有时会给我一些奇怪的错误，它找不到一个引用的程序集，不能写一个，或者现在最常写（几乎100％的时间）：尝试启动编译时发生了故障。

但实际上编译似乎已成功完成。我已经获得了一个新创建的exe，它运行得很好，即使在Visual Studio中的调试模式下也是如此。

在错误导致我进入这个KB之前文章，但是

症状

是相似的我已经检查了所有内容并且它似乎没有适用。

（程序集的一个

是96k编译的。）
http://support.microsoft.com/default...b;en-us;313512

我以前也遇到过这个问题。它似乎现在已经解决了，但也许

仍然以某种方式相关：
http://support.microsoft.com/default...b;en-us;825007

现在这主要是一个很大的新生，因为尽管有这样的信息，一切通常都很好。
很好。有时我必须退出并重新加载VS才能再次编译它，这真的很烦人。

有什么建议吗？

是的，构建顺序看起来很好。


问题非常一致。如果我按照我提到的步骤进行操作，每次都会获得相同的结果

。我在这些步骤中也有一致的解决方法，但它很快就会成为一个主要的痛苦，因为它现在100％的时间发生了现在。

。


" Rachel Suddeth" < RA **** @ bldhound.com>在消息中写道

新闻：OC ************* @ tk2msftngp13.phx.gbl ...

我假设你已经检查了你的构建顺序，对吧？

我认为没有任何完全可以解决这个问题的方法（但是如果有人知道的话，我会好好看看。）但是，有时我发现当我不能重建时，我可以建立。然后我通常会离开VS并且
重新进入。（并不是说我有理由这样做，它更像是我在构建过程需要时执行的宗教仪式
已清理过。之后，重建通常似乎有效。

希望这会有所帮助......
-Rachel

I have a solution consisting of 9 projects with various references to each
other (clean though, no loops, etc.). Visual Studio sometimes gives me
weird errors that it can''t find one of the referenced assemblies, can''t
write one, or now most frequently (almost 100% of the time): "A failure
occurred while attempting to start the compilation".

But in fact the compilation appears to have completed successfully. I''ve
got a freshly created exe and it runs just fine, even in debug mode from
within Visual Studio.

Before the errors have led to me to this KB article, but while the symptoms
were similar I''ve checked everything out and it doesn''t seem to apply. (One
of the assemblies is 96k compiled.)
http://support.microsoft.com/default...b;en-us;313512

I also previously had this problem. It seems to be solved now, but maybe is
still somehow related:
http://support.microsoft.com/default...b;en-us;825007

Right now this is mostly a big nuissance, as everything usually works fine
in spite of the message. Sometimes I have to exit and reload VS to get it
to compile again, which is just getting really annoying.

Any suggestions?

解决方案

Correction:

When I do a Rebuild Solution one of the assemblies is NOT rebuilt.

I deleted the .dll file from that project''s debug subfolder of the obj and
bin folders. When I restarted VS I of course got a couple messages that it
couldn''t find the assembly / dependency. Did Rebuild Solution. Everything
seems to have compiled, but VS still telling me it can''t find the assembly.

Exited and restarted VS and the message is gone. Rebuild Solution and I''m
back to the "failure" message on the same assembly, and it''s the only
assembly that didn''t recompile.

For whatever it''s worth, the assembly causing the problem is not the 96k
assembly, but it is referenced only by the 96k one. The 96k assembly also
references others.

"Daniel Billingsley" <dbillingsley@NO_durcon_SPAAMM.com> wrote in message
news:e9**************@TK2MSFTNGP14.phx.gbl...

I have a solution consisting of 9 projects with various references to each
other (clean though, no loops, etc.). Visual Studio sometimes gives me
weird errors that it can''t find one of the referenced assemblies, can''t
write one, or now most frequently (almost 100% of the time): "A failure
occurred while attempting to start the compilation".

But in fact the compilation appears to have completed successfully. I''ve
got a freshly created exe and it runs just fine, even in debug mode from
within Visual Studio.

Before the errors have led to me to this KB article, but while the symptoms were similar I''ve checked everything out and it doesn''t seem to apply. (One of the assemblies is 96k compiled.)
http://support.microsoft.com/default...b;en-us;313512

I also previously had this problem. It seems to be solved now, but maybe is still somehow related:
http://support.microsoft.com/default...b;en-us;825007

Right now this is mostly a big nuissance, as everything usually works fine
in spite of the message. Sometimes I have to exit and reload VS to get it
to compile again, which is just getting really annoying.

Any suggestions?

I assume you''ve checked your build order, right?

I don''t think there''s any complete cure for this problem (but I''ll be
watching in case someone knows better.) However, sometimes I''ve found that
when I can''t "rebuild", I can "build". Then I usually get out of VS and come
back in. (Not that I have a reason for doing this, it''s more like a
religious ritual that I perform whenever my build process needs to be
"cleansed.") After that, rebuild usually seems to work.

Hope this helps...
-Rachel

"Daniel Billingsley" <dbillingsley@NO_durcon_SPAAMM.com> wrote in message
news:uH**************@TK2MSFTNGP10.phx.gbl...

Correction:

When I do a Rebuild Solution one of the assemblies is NOT rebuilt.

I deleted the .dll file from that project''s debug subfolder of the obj and
bin folders. When I restarted VS I of course got a couple messages that
it
couldn''t find the assembly / dependency. Did Rebuild Solution.
Everything
seems to have compiled, but VS still telling me it can''t find the
assembly.

Exited and restarted VS and the message is gone. Rebuild Solution and I''m
back to the "failure" message on the same assembly, and it''s the only
assembly that didn''t recompile.

For whatever it''s worth, the assembly causing the problem is not the 96k
assembly, but it is referenced only by the 96k one. The 96k assembly also
references others.

"Daniel Billingsley" <dbillingsley@NO_durcon_SPAAMM.com> wrote in message
news:e9**************@TK2MSFTNGP14.phx.gbl...

I have a solution consisting of 9 projects with various references to
each
other (clean though, no loops, etc.). Visual Studio sometimes gives me
weird errors that it can''t find one of the referenced assemblies, can''t
write one, or now most frequently (almost 100% of the time): "A failure
occurred while attempting to start the compilation".

But in fact the compilation appears to have completed successfully. I''ve
got a freshly created exe and it runs just fine, even in debug mode from
within Visual Studio.

Before the errors have led to me to this KB article, but while the

symptoms

were similar I''ve checked everything out and it doesn''t seem to apply.

(One

of the assemblies is 96k compiled.)
http://support.microsoft.com/default...b;en-us;313512

I also previously had this problem. It seems to be solved now, but maybe

is

still somehow related:
http://support.microsoft.com/default...b;en-us;825007

Right now this is mostly a big nuissance, as everything usually works
fine
in spite of the message. Sometimes I have to exit and reload VS to get
it
to compile again, which is just getting really annoying.

Any suggestions?

Yeah, the build order looks fine.

The problem is very consistent. If I do the steps I mentioned I get the
same results every time. I also have a consistent workaround in those
steps, but it''s quickly becoming a major pain as it happens 100% of the time
now.

"Rachel Suddeth" <ra****@bldhound.com> wrote in message
news:OC*************@tk2msftngp13.phx.gbl...

I assume you''ve checked your build order, right?

I don''t think there''s any complete cure for this problem (but I''ll be
watching in case someone knows better.) However, sometimes I''ve found that
when I can''t "rebuild", I can "build". Then I usually get out of VS and come back in. (Not that I have a reason for doing this, it''s more like a
religious ritual that I perform whenever my build process needs to be
"cleansed.") After that, rebuild usually seems to work.

Hope this helps...
-Rachel

这篇关于编译问题，或者是吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！