Issue with setting the assembly version

FinalBuilder Bugs
1

Hello everyone

I’m using finalbuilder to build VS2010 solutions (using the Build VS.Net Solution Action) and we’re dynamically setting the Assembly Version and File Version. This is done by using Project variables. We have multiple branches for a line of code and we want them to build to the same minor version. When I run this locally, it all works great. But when this is run on Final Builder Server it’s not being set correctly.

The versions are being set as follows:
Minor: %AssemblyVersionMinorBuild%
Build: %AssemblyVersionBuild%
Revision: Auto Increment

I’ve attached screen shots of the local build: [IMAGE:487]

and the Server build log: [IMAGE:488]

It appears the server is using the AssemblyVersonMinor variable for the Minor version and the local is using the AssemblyVersion MinorBuild but I’ve verified that the local version of the project and the server version are the same. Any help on why the server build is pulling a different Minor Version would be greatly appreciated.

Thanks

FB Version: 7.0.0.1864
Win Version: 7 SP1

2

Hi Tim,

What is the %AssemblyVersionMinor% used for in your scripts? It seems like it might be used differently in the server version file compared to the desktop version.

Also is there any part of your script which relies on environment. Typically what I find is that some value is being set because of a condition in the script which isn’t met on a specific machine. E.g. File being present.

3

Hi Jason

The %AssemblyVersionMinor% is used to to tell FinalBuilder what branch of code to pull from TFS. It is used the same way in both server and Local version. We use the TFS branch name for the Minor version; since the .rel is invalid for a version, we update it and store it in %AssemblyVersionMinorBuild% which is used in the Build VS.NEt solultion action to set the version.

Nothing in the script depends on enviroment, the only things that change between local workstation and server builds are the variables being used.

After messing with this for way to long, I created a new Build VS.Net Solution action and removed the old one. That fixed the issue, I guess something had gotten corrupted in it.

Thanks
Tim