问题描述
所以，比方说，我有一个构建定义变量 BuildOutputDirectory = $（Build.SourcesDirectory）\ $（system.teamProject）\ $（Build.DefinitionName）\ $（BuildConfiguration），在两个构建步骤中使用它，Visual Studio Build和Command Line Build。
So, say, I have a build definition variable BuildOutputDirectory = $(Build.SourcesDirectory)\$(system.teamProject)\$(Build.DefinitionName)\$(BuildConfiguration), to use it in two build steps, Visual Studio Build, and Command Line Build.
问题是变量引用$（BuildOutputDirectory）在命令行步骤中正确扩展（参数：$（BuildOutputDirectory）\ * .msi $（DropFolder）\），而不是在Visual Studio Build中（MsBuild参数： / p：OutDir = $（BuildOutputDirectory）
- 逐字传递给MsBuild）。那么它必须是Visual Studio Build步骤实现的特定内容吗？
The problem is that the variable reference $(BuildOutputDirectory) gets properly expanded in Command Line step (Arguments: $(BuildOutputDirectory)\*.msi $(DropFolder)\), while not in Visual Studio Build (MsBuild Arguments: /p:OutDir=$(BuildOutputDirectory) - gets passed to MsBuild verbatim). So it must be something specific to Visual Studio Build step implementation?
是否有解决MsBuild Arguments问题的方法？
Is there a way around the MsBuild Arguments problem?
推荐答案
感谢您在此发帖。
您能告诉我您的步骤截图吗？根据您的描述，您的Visual Studio Build步骤似乎没有错，您能否解释一下您的问题？
Could you please give me a screenshot of your steps? And according to your description, it seems nothing wrong with your Visual Studio Build step, so could you explain your questions?
这篇关于TFS 2015 Visual Studio构建步骤不评估变量的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！