下面的方法对我很有效:

简单地从发布>调试>发布(反之亦然)更改，然后发布。

不需要删除，编辑，发布任何你不需要的东西。

我发现我可以通过改变目标位置从obj/[释放|阶段|..]到解决方案文件夹之外的新路径，例如c:\deployment。看起来VS 2012有点混乱，可能在发布过程中就放弃了。

Matt

最近在VS 2013的一个MVC项目中，我导入了Umbraco CMS，遇到了同样的问题。我不能出版。上面的答案很有帮助，尽管我需要一段时间来弄清楚我在vs中应该做什么。这需要一些研究，比如在MS博客上找到答案。我试着简单地说:

Choose in the VS toolbar a certain configuration e.g. Release and Any CPU. Run the project. Afterwards right-click in the Solution Explorer on the solution in question, choose Publish. Create a new publishing profile or use a given one, but always make sure that in the settings the same configuration (e.g. Release and Any CPU) is chosen, as before you run the project the last time. Additionally in my case it was necessary to delete the OBJ folder because here the settings from my last unsuccessful tries to publish got stuck, though I restarted VS and deleting all publishing profiles.

我也遇到了同样的问题。以上的方法对我来说都没用。

因此，我已经排除了在发布时未能复制的文件。

这可能是由vs2012的RC创建的解决方案/项目造成的。这在几个月前发生在我身上，通过确保我的解决方案构建配置与我的项目配置匹配来解决这个问题……

我最近在使用VS2012 Express for Web打开vs2012RC中最初创建的相同解决方案时遇到了同样的问题。我完全按照最初海报上的建议做了，它解决了我的问题。

下面是我找到答案的线索:

connect.microsoft.com/VisualStudio/feedback/details/746321/publish-web-application-fails

上述对话中对我有帮助的中肯回答是:

Posted by Microsoft on 6/13/2012 at 12:00 PM Hi Andrew, This was a bug in how we handle the solution configuration vs. the project configuration. We incorrectly assumed that they would be the same (e.g. Solution's Release|x86 would have each project set to Release|x86 as well), which caused us to use the wrong build properties for publishing files. The workaround is to make the solution configuration and build configuration match. This issue will be fixed in the next release of Visual Studio 2012. Thanks, - Jimmy Lewis SDET, Visual Web Developer team

同样的问题。解决方法是将发布设置从发布更改为调试。重新发布，然后改回发布…