msbuild 14:GenerateProjectSpecificOutputFolder [英] msbuild 14 : GenerateProjectSpecificOutputFolder
问题描述
MSBUILD 14是否仍然遵守 GenerateProjectSpecificOutputFolder参数?
does MSBUILD 14 still honor the GenerateProjectSpecificOutputFolder parameter?
之前我在TFS2013 / VS2013上成功使用了它。一个SLN会将每个项目构建到BIN下的子文件夹中。
Previously I used this successfully with TFS2013/VS2013. One SLN would build each project to a subfolder under BIN.
现在尝试使用TFS2015 / VS2015。 MSBUILD的参数是:
Trying this now with TFS2015/VS2015. Parameters for MSBUILD are:
/ p:OutputPath = $(Build.BinariesDirectory / p:GenerateProjectSpecificOutputFolder = True
/p:OutputPath=$(Build.BinariesDirectory /p:GenerateProjectSpecificOutputFolder=True
输出将转到\\ \\ b\文件夹,但没有子文件夹。一切都是在根目录中构建的。
The output is going to the \b\ folder, but there are no subfolders. Everything is built in the root.
我可以使用VS2015获得相同的行为吗?
Can I have the same behaviour using VS2015?
谢谢,
Dave
Dave S。
推荐答案
嗨Dace,
感谢您在此发帖。
我认为您使用/ p:GenerateProjectSpecificOutputFolder = True到m在drop文件夹中输出。您仍然可以使用TFS2015 XAML
build中的参数。但是在Vnext Build中,更容易管理构建工件。您可以使用
复制和发布构建工件任务来管理构建工件:
I think you used /p:GenerateProjectSpecificOutputFolder=True to manage the output in drop folder. You could still use the parameters in TFS2015 XAML build. But in Vnext Build, there much be easier to manage the build artifacts. You could use the Copy And Publish Build Artifacts task to manage the build artifacts:
通过此任务,您可以在路径中获得所需的结果
With this task, you could get the result you want in the path
(Build.BinariesDirectory):
(Build.BinariesDirectory):
最好的问候
Limitxiao Gao
Limitxiao Gao
这篇关于msbuild 14:GenerateProjectSpecificOutputFolder的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!