TeamCity-AssemblyInfoPatcher不起作用，记录错误 [英] TeamCity - AssemblyInfoPatcher not working, error is logged

问题描述

AssemblyInfoPatcher构建功能不起作用.有些文件已打补丁，有些则未打补丁.

The AssemblyInfoPatcher build feature isn't working. Some files are patched and some are not.

Assembly file version was specified, but couldn't be patched in file D:\TeamCity\Agent\buildAgent\work\6afd998e316c631f\La\Di\Da\Properties\AssemblyInfo.cs. Is necessary attribute missing?

我认为这是因为它是1.0.*，因为其中一个失败的文件具有这种格式，而其中一个成功的文件具有默认的1.0.0.0格式，因此我在整个解决方案中将属性更改为1.0.0.0现在它们都不起作用.

I thought it was because it was 1.0.* since one of the failed files had this format, and one of the successful ones had the default 1.0.0.0 format, so I changed the attribute to 1.0.0.0 across the entire solution and now none of them work.

我收到以上错误或:

Assembly version attributes were not found in ...

该属性已定义，并且团队中至少有两个人确认他们也可以使用生产用眼睛看到该属性.

The attribute is defined and at least two other people on the team have confirmed that they can also see it using their production eyes.

很高兴积the现金，以便砸碎工作键盘.

Happy to stump up the cash so I can smash my work keyboard.

推荐答案

好吧，我设法使其正常运行.

Well, I managed to get it working but not.

我有一个称为AssemblyVersionStringWithCounter的配置参数，该参数是从PowerShell脚本设置的.我在修补程序功能中使用了此功能.

I had a Configuration Parameter called AssemblyVersionStringWithCounter that I set from a PowerShell script. I was using this in the patcher feature.

我将其更改为由其他参数组成，例如

I changed it to be composed of other parameters like

%MajorVersionNumber%.%MinorVersionNumber%.%BuildWeek%.%build.counter%

现在它修改了文件，但未设置参数，版本不正确.似乎AssemblyInfoPatcher无法使用在构建步骤中设置的值.

And now it mods the files but the params are not set, the version is incorrect. Seems the AssemblyInfoPatcher cannot use values set during the build steps.

当我从一开始就应该使用PowerShell时，似乎浪费了我客户大约800英镑的钱.代码为王.

Seems I've wasted about £800 of my client's money when I should have just PowerShelled it from the start. Code is King.

这篇关于TeamCity-AssemblyInfoPatcher不起作用，记录错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！