使用 MsBuild 复制文件
我有两个项目的解决方案。其中之一是一个简单的项目，不依赖于任何特殊的程序集来构建。但是，应用程序可以启动外部可执行文件（我也拥有它——这是我的解决方案的第二个项目）。当我构建项目时，我希望将外部项目的可执行文件（+依赖项，例如 app.config）复制到我的项目的目标目录下。
我如何使用 MsBuild 实现这一目标？我的第一个想法是添加对可执行文件的引用（即使我不需要它来构建）来复制文件。这对我来说似乎有点老套。
谢谢！
PS 另一个问题：假设我可以告诉 MsBuild 复制可执行文件。如果可执行文件未构建怎么办？我可以强制它构建吗？
I have a solution with two projects. One of them is a simple project that doesn't depend on any special assemblies to build. However, the application is allowed to launch an external executable (that I also own -- this is the second project of my solution). When I build the project, I would like the executable (+ dependencies such as app.config) of the external project to be copied under the target directory of my project.
How can I achieve this with MsBuild? My first idea was to add a reference to the executable (even though I don't need it to build) to copy the file. This seem a bit hacky to me.
Thanks!
P.S. Another question: Let's say that I can tell MsBuild to copy the executable. What if the executable isn't build? Can I force it to build?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
在您的情况下，您应该让 MSBuild 脚本替换您的解决方案并在那里声明所需的依赖项：
...并且您可以指示第二个项目的目标将其输出复制到所需的位置。您甚至可以指示第一个项目将其输出路径存储到一个变量中，以便在复制第二个项目的输出（DestinationFolder）时使用。
In your case you should make your MSBuild script replace your solution and declare the desired dependency there:
... and you can instruct the target of your second project to copy its output to the desired location. You could even instruct your first project to store its output path into a variable to use when copying the output of your second project (DestinationFolder).
您是否查看过 MSBuild 复制任务：复制任务 ？
Have you looked the MSBuild Copy Task: Copy Task ?
如果您对@Filburt 的回答感到满意，我可以建议改进这个解决方案。
如果您查看默认构建目标的工作原理：
您会看到构建或重建目标的唯一输出是$(TargetPath)。
$(TargetPath) 是构建的程序集的完整路径。要更改此行为，您可以破解构建过程。但在项目B中定义自己的目标会更简单：
在A项目中只需定义AfterBuild目标：
此解决方案不需要创建自定义构建脚本。直接在VS中得到结果。
If you will be satisfied with @Filburt answer I can suggest to improve this solution.
If you'll take a look how default Build target works:
You'll see that the only output from build or rebuild target is $(TargetPath).
$(TargetPath) is a full path to the built assembly. To change this behaviour you can hack build process. But it will be match simpler to define your own target in project B:
In A project just define AfterBuild target:
This solution doesn't require to create custom build script. You will get the result directly in VS.