我有此错误MSB3073(请帮助)文件在这里 [英] I have this Error MSB3073 (Please Help) File here

问题描述

你好，我尝试了所有可以解决的问题，请

C:\ Program Files(x86)\ MSBuild \ Microsoft.Cpp \ v4.0 \ Microsoft.CppCommon.targets(103,5):错误MSB3073:命令"pushd" C:\ Users \ Admistrator \ Desktop \ mw2 \ AlterIWnet源代码\ alterIWnet \ iw4 \ iw4 \ clientdll \\ dependencies \ tools"

1> C:\ Program Files(x86)\ MSBuild \ Microsoft.Cpp \ v4.0 \ Microsoft.CppCommon.targets(103,5):错误MSB3073:调用

"C:\ Users \ Admistrator \ Desktop \ mw2 \ AlterIWnet源代码\ alterIWnet \ iw4 \ iw4 \ clientdll \\ dependencies \ tools \ svnrev.cmd"

1> C:\ Program Files(x86)\ MSBuild \ Microsoft.Cpp \ v4.0 \ Microsoft.CppCommon.targets(103,5):错误MSB3073:popd

1> C:\ Program Files(x86)\ MSBuild \ Microsoft.Cpp
\ v4.0 \ Microsoft.CppCommon.targets(103,5):错误MSB3073:

1> C:\ Program Files(x86)\ MSBuild \ Microsoft.Cpp
\ v4.0 \ Microsoft.CppCommon.targets(103,5):错误MSB3073::VCEnd退出，代码为255.

在此处下载文件:
http://www.mediafire.com/?x0iedt1se6cv9f3 [解决方案

PUSHD [ ^ ]是CMD.exe内部的命令.

这也适用于通话和弹出.

因此MSBuild找不到它们，因为没有call.exe，pushd.exe或popd.exe

最好的问候
Espen Harlinn

正如我所料，问题是自定义构建步骤，请参见"svnrev.cmd".
乍一看很难说是做什么的，但是Subversion可以做些什么.

这是一个常见的错误(但是不是很常见)，它试图通过在其中包含Subversion命令来过度构建该构建.这在方法上是非常危险的构想.修订控制系统应完全独立于项目/解决方案.我建议你摆脱它.不，我总是一键式构建和填充，但是您应该将两者分开.

考虑您经常执行以下循环:从Subversion获取新代码并进行构建.例如，您可能必须批处理文件，一个要获取代码，另一个要"build_all".如果您经常执行整个周期，请再创建一个批处理文件，然后再调用另外两个.并且不要在项目中放置颠覆命令，而版本控制应该完全不可知.代码就是代码，它可以与project/solution目录中的内容一起使用，不是吗.

顺便说一句，您在"clientdll.rar"文件中的另一个地方误用了Subversion，因为所有这些".svn"子目录都在那里.从不复制工作目录，始终执行Subversion命令导出"，它将为您导出纯代码.另外，总是知道什么是源代码，什么是临时文件.例如，从不交付(也从不存储在代码库中)"*.suo"，"*.user"，"bin"，"obj"等.

—SA

使用pushd命令检查您尝试切换到的路径，以确保它们有效且可访问.

Hello i tryed everything can someone fix it Please

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(103,5): error MSB3073: The command "pushd "C:\Users\Admistrator\Desktop\mw2\AlterIWnet Source Code\alterIWnet\iw4\iw4\clientdll\\dependencies\tools"

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(103,5): error MSB3073: call

"C:\Users\Admistrator\Desktop\mw2\AlterIWnet Source Code\alterIWnet\iw4\iw4\clientdll\\dependencies\tools\svnrev.cmd"

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(103,5): error MSB3073: popd

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp
\v4.0\Microsoft.CppCommon.targets(103,5): error MSB3073:

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp
\v4.0\Microsoft.CppCommon.targets(103,5): error MSB3073: :VCEnd" exited with code 255.

Download File Here:
http://www.mediafire.com/?x0iedt1se6cv9f3[^]

解决方案

PUSHD[^] is a command that''s internal to CMD.exe.

This goes for call and popd too.

So MSBuild can''t find them, as there is no call.exe, pushd.exe or popd.exe

Best regards
Espen Harlinn

As I expected, the problem is a custom build step, see "svnrev.cmd".
Hard to say at first glance what is does, but it does something with Subversion.

This is a common (however not very frequent) mistake to try to over-engineer the build by including Subversion commands in it. This is methodically very dangerous conception. Revision control system should be totally independent from project/solution. I advise you get rid of it. No, I always do one-click build and stuff, but you should separate the two.

Consider you often do the cycle: get fresh code form Subversion and build it. For example, you can have to batch files, one to get code, another one — "build_all". If you often do the whole cycle, create one more batch file and call the other two. And don''t put subversion commands in the project, which should be totally agnostic to Revision Control. Code is code, it works with what is in the project/solution directory, isn''t it.

By the way, you misused Subversion in one more place, in your "clientdll.rar" file, as all those ".svn" sub-directories are there. Never copy working directory, always perform Subversion command "Export", which will export pure code for you. Also, always know what is source code, what is temporary file. For example, never deliver (and never store in code base) "*.suo", "*.user", "bin", "obj", etc.

—SA

Check the paths that you are trying to switch into with the pushd command(s) to ensure they are valid and accessible.

这篇关于我有此错误MSB3073(请帮助)文件在这里的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！