AssemblyInfo patcher works on Windows but not on Mac OSX

I have a Xamarin projectthat uses team city to set the build number. It seesm to work on Windows 2012 build server, but fails when run on the MacOS X build server. We used to do this manually using a sed script, but the iOS build guys wanted to use the AssemblyInfo patcher like we do on Windows & android builds.

On Windows I get:

[14:51:16]Checkout directory: F:\TeamCity\buildAgent\work\13745002b1a25a84

...

[14:51:17][Step 1/3] Update assembly versions: scanning checkout directory for AssemblyInfo files to update version to 1.6.4976.0408 (25s)

[14:51:19][Update assembly versions] Updating assembly version in F:\TeamCity\buildAgent\work\13745002b1a25a84\[snip]\AssemblyInfo.cs

[14:51:19][Update assembly versions] Assembly  version attributes were not found in  F:\TeamCity\buildAgent\work\13745002b1a25a84\[snip]\Properties\AssemblyInfo.cs

[14:51:20][Update assembly versions] Updating  assembly version in  F:\TeamCity\buildAgent\work\13745002b1a25a84\[snip]\Properties\AssemblyInfo.cs

[14:51:20][Update assembly versions] Assembly  version attributes were not found in  F:\TeamCity\buildAgent\work\13745002b1a25a84\[snip]\Properties\AssemblyInfo.cs

[snip 30 more]


On MacOS X I get:

[14:49:57]Checkout directory: /Applications/buildAgent/work/13745002b1a25a84
...

[14:54:06][Step 1/5] Update assembly versions: scanning checkout directory for AssemblyInfo files to update version to 1.6.5003.0409

[14:54:06][Update assembly versions] Found no AssemblyInfo.* files under Properties folders


Has anyone made AssemblyInfo patcher work on a MacOSX build, if so what did you do? I was wondering if there was a base directory you needed to have set (or something like that) but I've not managed to work it out yet.

2 comments
Comment actions Permalink

I've just run into the same issue. How does AssemblyInfo Patcher look for files? Why doesn't it find any on OS X?

We are using TeamCity 8.0.4.

-Michael

0

Please sign in to leave a comment.