Assembly Info Patcher & Linked AssemblyInfo.cs
Hi,
We have a linked assembly info across projects and was wondering if I could use the assembly info patcher on the same. Looks like there is a restrictrion on the name that the patcher looks for. Our linked file is called GlobalAssemblyInfo.cs.
Any suggestions on the same is greatly appreciated.
Thanks,
Balaji
Please sign in to leave a comment.
The documentation states that the patcher only works with standard VS projects, so I guess you cannot solve this problem. The AssemblyInfo Patcher is a nice addition, although I think it still needs some improvements to become really usable, like allowing some more versioning customization, ignoring the AssemblyVersion attribute, etc.
JMHO.
My thoughts exactly. So I went ahead and added a new powershell build step to patch the file myself. The script takes in the version number as an argument.
Cheers,
Balaji
We've been following this article for quite some time now. Works well enough for us.
http://blog.benhall.me.uk/2008/06/team-city-update-assemblyinfo-with.html
Hi Matt,
We had a similar setup with CruiseControl.NET and MSBuild. But since moving to Teamcity, we are using the sln file to build the project and not MSBuild. In that case smething like the script above should help.
Cheers,
Balaji
I use a similar approach, instead of creating a new AssemblyInfo file, I modify the existing one with the FileUpdate task of the MSBuildCommunityTasks package.
We would really appreciate if you create a feature request in our tracker and describe there what is currently missing in the Assembly Info patcher. This would help us a lot to make it more flexible.