TeamCity 的 AssemblyInfo 修补程序的数字格式 [英] TeamCity's AssemblyInfo patcher's number format

问题描述

我曾经让 TeamCity + WiX + MSBuild 社区任务工作.现在我已经升级到 WiX 3.5，我不记得我是如何配置它的.:) 当我浏览 TeamCity 时，我遇到了AssemblyInfo Patcher".我想，太棒了！这会让我的生活更轻松！".我使用 %build.vcs.number.1% 作为格式并构建了我的安装程序.

I once had TeamCity + WiX + MSBuild Community Tasks working. Now that I've upgraded to WiX 3.5, I can't remember how I had configured it. :) As I was poking through TeamCity, I came across the "AssemblyInfo Patcher". I thought, "Great! This will make my life much easier!". I used %build.vcs.number.1% for the format and built my installer.

虽然修补程序确实提取了 vcs 编号，但它使用它作为版本中的主要编号.因此，它生成了 xxxx.0.0.0 版本而不是 1.0.0.xxxx.

While the patcher did pull in the vcs number, it used it for the major number in the version. So instead of 1.0.0.xxxx, it made the version xxxx.0.0.0.

我浏览了 JetBrain 的文档站点，并没有想出与将其更改为更合适的设置相关的任何内容.我也寻找正则表达式支持，但没有找到任何东西.

I looked through JetBrain's documentation site and came up with nothing related to changing this to a more appropriate setting. I also looked for regex support, but didn't find anything.

谁能提出一个好的解决方案，还是我应该回去尝试配置我的原始工具集?

Can anyone suggest a good solution, or should I just go back to trying to configure my original set of tools?

推荐答案

程序集信息修补程序一次只修补完整的版本字符串.但是系统变量build.number可以从build配置的general"页面生成，像这样:

The assembly info patcher only patches the complete version string at once. But the system variable build.number can be generated from the "general" page of the build configuration, like this:

当您将 %build.number% 指定为您的 AssemblyInfo 版本时，它将从您的常规设置页面中获取组合编号.

When you specify %build.number% as your AssemblyInfo version, it will pick up the combined number from your General settings page.

这篇关于TeamCity 的 AssemblyInfo 修补程序的数字格式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！