blocks|key|4227220|text|第一步是弄清楚错误到底是什么。为了做到这一点，将MsBuild输出展开为诊断性输出。这将显示实际执行的命令，并希望完整的错误消息也会显示出来。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4227221|工具->选项|unordered-list-item|4227222|项目和解决方案->的构建和运行|4227223|将"MsBuild项目生成输出的详细性“更改为”诊断“。|4227224|4227225|4227226|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|P|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

The first step is figuring out what the error actually is. In order to do this expand your MsBuild output to be diagnostic. This will reveal the actual command executed and hopefully the full error message as well

<ul>
<li>Tools -> Options </li>
<li>Projects and Solutions -> Build and Run</li>
<li>Change "MsBuild project build output verbosity" to "Diagnostic". </li>
</ul>

blocks|key|1760572|text|右键单击项目->属性->生成事件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760573|删除生成后事件命令行文本块中的文本|1760574|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|$]]

Right click project -> Properties -> Build Events

Remove the text in Post-build event command line text block

blocks|key|4227371|text|对于我:我在路径的文件夹名G:\Other+Imp+Projects\Mi.....中有一个空白|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4227372|解决方案1+:|BOLD|4227373|从文件夹中删除空白|4227374|例子：Other+Imp+Projects+->>+Other_Imp_Projects|4227375|解决方案2:|4227376|添加引号("")作为您的路径。|4227377|示例：mkdir+"$(ProjectDir)$(OutDir)Configurations"+//见双引号|4227378|entityMap^0|D|T|0|0|7|0|0|3|I|Q|I|0|0|6|0|5|2|0|3|18|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|10|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|16|8|@$9|17|A|18|B|H]]|D|@]|E|$]]|$1|O|3|P|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|T|$]]

For me : I have a white space in my path's folder name <code>G:\Other Imp Projects\Mi.....</code>

<h2>Solution 1 :</h2>

Remove white space from folder 

Example: <code>Other Imp Projects</code> ->> <code>Other_Imp_Projects</code>

<h2>Solution 2:</h2>

add Quote (<code>""</code>) for your path.

Example: <code>mkdir "$(ProjectDir)$(OutDir)Configurations"</code> //see double quotes

blocks|key|1217240|text|尝试以管理员身份打开。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1217241|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|$]]

Try to open Visual Studio as admin.

blocks|key|4227244|text|对我来说，在VS+2013中，我必须消除UI项目(MVC)中引用中缺少的引用。原来失踪的那些没有被引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4227245|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|$]]

For me, in VS 2013, I had to get rid of missing references under References in the UI project (MVC). Turns out, the ones missing were not referenced.

blocks|key|1760628|text|我知道这已经太迟了，但是，这也能帮助到别人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760629|在我的例子中，我发现源文件正在被另一个进程使用，该进程限制复制到目标。我发现通过使用命令提示符(只需将post+build命令复制到命令提示符并执行，就会给出错误信息)。|1760630|确保您可以从命令提示符复制，|1760631|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|$]]

I know this is too late for sure, but, this could help someone as well. 

In my case, i found that the source file is being used by another process which was restricting from copying to the destination. I found that by using command prompt ( just copy paste the post build command to the command prompt and executed gave me the error info). 

Make sure that you can copy from the command prompt,

blocks|key|1217391|text|这建立在JaredPar的答案之上.是给VS2017的。Visual+2017中也有相同的“生成和运行”选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1217392|，命令"chmod+%2Bx“与代码1一起退出。|1217393|在build窗口中，我搜索了"Error“，并在相同的一般区域中发现了一些错误。我能够单击构建输出中的一个链接，并发现错误涉及.targets文件中的这个条目：|1217394|++<Target+Name="ChmodChromeDriver"+BeforeTargets="BeforeBuild"+Condition="'$(WebDriverPlatform)'+!=+'win32'">
++++<Exec+Command="chmod+%2Bx+&quot;$(ChromeDriverSrcPath)&quot;"+/>
++</Target>|code-block|syntax|javascript|1217395|在构建输出中，我还发现了一条更详细的错误消息，该消息本质上说它无法在它正在查找的packages文件夹中找到Selenium.WebDriver.ChromeDriver+v2.36。我检查了项目的NuGet包，版本2.36确实在已安装的软件包列表中。我找到了2.36的包文件，并将文件夹、子文件夹和文件的属性从“只读”更改为“读/写”。建造，但同样的失败。有时，“更新”到包的不同版本，然后更新回原始版本可以修复这种类型的错误。因此，我将管理NuGet包中的引用“更新”为2.37，生成，失败，然后“更新”回2.36，构建成功，没有"chmod+%2Bx“错误消息。|1217396|我正在构建的项目是基于Visual模板的Appium测试工具，模板名为"Develop_Automated_Test“。|1217397|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

This builds on the answer from JaredPar... and is for VS2017. The same "Build and Run" options are present in Visual Studio 2017.

I was getting, The command "chmod +x """ exited with code 1

In the build output window, I searched for "Error" and found a few errors in the same general area. I was able to click on a link in the build output, and found that the error involved this entry in the .targets file:

<pre><code> &lt;Target Name="ChmodChromeDriver" BeforeTargets="BeforeBuild" Condition="'$(WebDriverPlatform)' != 'win32'"&gt;
 &lt;Exec Command="chmod +x &amp;quot;$(ChromeDriverSrcPath)&amp;quot;" /&gt;
 &lt;/Target&gt;
</code></pre>

In the build output, I also found a more detailed error message that essentially stated that it couldn't find Selenium.WebDriver.ChromeDriver v2.36 in the packages folder it was looking in. I checked the project's NuGet packages, and version 2.36 was indeed in the list of installed packages. I did find the package files for 2.36, and changed the attributes on the folder, subfolders and files from "Read Only" to "Read/Write". Built, but same failure. Sometimes "updating" to a different version of the package and then updating back to the original can fix this type of error. So I "updated" the reference in Manage NuGet packages to 2.37, built, failed, then "updated" back to 2.36, built, and the build succeeded without the "chmod +x" error message.

The project I was building was based on a Visual Studio Project template for Appium test tooling, template name "Develop_Automated_Test".

blocks|key|1217422|text|检查您的路径：如果您正在为TFS使用单独的构建服务器(很可能)，请确保.csproj文件中的所有路径与TFS服务器路径相匹配。当*.csproj文件具有对我的开发机器路径(而不是TFS服务器路径)的引用时，我在签入该文件时出现了上述错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1217423|删除多行命令：同时，尝试将多行命令删除为xml中的单行命令，以防万一。我在*.proj中使用了以下xml，这导致了TFS中的问题：|1217424|<Exec+Condition="bl.."+
Command="+Blah...
..."+</Exec>|code-block|syntax|javascript|1217425|将上面的xml更改为这样做是有效的：|1217426|++<Exec+Condition="bl.."+Command="+Blah..."+</Exec>|1217427|entityMap^0|0|6|1F|6|0|0|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|R|$]]

Check your paths:
If you are using a separate build server for TFS (most likely), make sure that all your paths in the .csproj file match the TFS server paths. I got the above error when checking in the *.csproj file when it had references to my development machine paths and not the TFS server paths.

Remove multi-line commands: Also, try and remove multi-line commands into single-line commands in xml as a precaution. I had the following xml in the *.proj that caused issues in TFS:

<pre><code>&lt;Exec Condition="bl.." 
Command=" Blah...
..." &lt;/Exec&gt;
</code></pre>

Changing the above xml to this worked:

<pre><code> &lt;Exec Condition="bl.." Command=" Blah..." &lt;/Exec&gt;
</code></pre>

blocks|key|1760815|text|我也有过同样的问题。尝试了以上所有的答案。它实际上是抱怨一个.dll文件。我在Visual中清理了项目，但是.dll文件仍然保留下来，所以我从bin文件夹中手动删除了它，并且它工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760816|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 the same issue. Tried all the above answers. It was actually complained about a .dll file. I clean the project in Visual Studio but the .dll file still remains, so I deleted in manually from the bin folder and it worked.

blocks|key|1760831|text|希望这对某人有所帮助，但我有预构建事件和发布构建事件，它一直抱怨一个名为"Microsoft.Common.CurrentVersion.targets“的文件--目标"CoreBuild”不存在于项目中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760832|以下是我为解决这个问题所做的努力：|1760833|关闭项目|ordered-list-item|1760834|删除.suo文件(它重新生成)|1760835|请一位团队成员提供该文件的副本(Microsoft.Common.CurrentVersion.targets)+--我的不一样--我拿走了他的。|1760836|它已经编好了-很好。|1760837|1760838|1760839|我一定是把文件弄坏了。|1760840|entityMap^0|0|0|0|0|0|0|0|0|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|F|7|U|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|X|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

Hope this helps someone, but I had prebuild events and post build events and it kept complaining about a file called &quot;Microsoft.Common.CurrentVersion.targets&quot; &quot;The target &quot;CoreBuild&quot; does not exist in the project&quot;.
Here's what I did to resolve it:
<ol>
<li>close the project</li>
<li>delete the .suo file (it regenerates)</li>
<li>Asked a team member to provide a copy of that file (Microsoft.Common.CurrentVersion.targets) - mine was different - I took his.</li>
<li>It compiled - good to go.</li>
</ol>
I must have wrecked that file somehow.

blocks|key|1760897|text|我的批处理文件中没有语法错误，它在cmd提示符外部VS上运行良好。所以最后，我加入了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760898|exit+0|code-block|syntax|javascript|1760899|若要在批处理文件的末尾显式返回成功代码，则该代码开始工作。|1760900|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

There was no syntax error in my batch file and it ran fine on a cmd prompt outside VS.
So finally, I added
<pre><code>exit 0
</code></pre>
to return a success code explicitly at the end of my batch file and it started working.

blocks|key|1760955|text|对我来说，相同版本的输出文件(.dll)已经存在，所以我猜它在覆盖方面有困难。尽管它以前从来没有做过。无论如何，删除现有的文件和运行重建修复它为我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760956|如果前面的方法没有修复它，我的下一个检查将是检查路径长度是否导致它。因此，必须将目标文件夹更改为类似桌面的某个位置，这样路径就不会太长。|1760957|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|$]]

For me the output file (.dll) of the same version already existed so I guess it was having trouble overwriting. Even though it has never done it before. Anyways, deleting the existing file and running Rebuild fixed it for me.
If the previous method wouldn't have fixed it, my next check would have been to check if the path length was causing it. So would have change the target folder to somewhere close like the Desktop so that the path isnt too long.

blocks|key|4227671|text|提示:在项目中搜索"Exec+Command=“|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4227672|在我的例子中，我在"Microsoft.Extensions.ApiDescription.Server.targets“文件中发现了下面的标记，我注意到了这一行，它适用于我：|4227673|<Exec+Command="$(_Command)"+LogStandardErrorAsError="true"+/>|code-block|syntax|javascript|4227674|entityMap^0|0|6|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Hint: Search for &quot;Exec Command=&quot; in your project
In my case I found following tag in &quot;Microsoft.Extensions.ApiDescription.Server.targets&quot; file, I remarked the line and it worked for me:
<pre><code>&lt;Exec Command=&quot;$(_Command)&quot; LogStandardErrorAsError=&quot;true&quot; /&gt;
</code></pre>

I've read around many questions but I've not been able to find the right answer for me.

As I try to compile a project in VS2012 I have this result:

The command "....\tools\bin\nuget pack Packages\Lib.Html.nuspec - OutputDirectory ....\bin\Zip\Packages -NoPackageAnalysis" exited with code 1.

I looked for the line of code in my .csproj file, where the error should be, and there is: 

<pre><code>&lt;Exec Command="$(ProjectDir)..\..\tools\bin\nuget pack $(ProjectDir)Packages\Lib.Html.nuspec -OutputDirectory $(OutputPath)Packages -NoPackageAnalysis" /&gt; 
</code></pre>

What am I doing wrong?

[EDIT] 
Launching the Debug of that project and ignoring "building errors", I have a new alert:

"Visual Studio cannot start debugging because the debug target '[project.exe path]' is missing.
Please build the project and retry, or set OutputPath and AssemblyName properties appropriately to point at the correct location for the target assembly."

How can I resolve the error: "The command [...] exited with code 1"?

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

我已经阅读了很多问题，但我一直未能找到正确的答案。当我试图用VS2012编译一个项目时，我得到了以下结果：命令"....\tools\bin\nuget pack Packages\Lib.Html.nuspec - OutputDirectory ....\bin\Zip\Packages -NoPackageAnalysis“与代码1一起退出。我查找了我的.csproj文件中的代码行(错误应该

问如何解决错误：“命令[.]与代码1一起退出”？
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解决错误：“命令[.]与代码1一起退出”？EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解决错误：“命令[.]与代码1一起退出”？
EN