Introducing assembly versioning as part of CI upgrade process

Jun 11, 2013 at 11:21 AM
I added the 2012 version which successfully updates the assembly version on the build server although I've had some issues using it with remote deployment. I added the assembly versioning to the upgrade build definition which updates the solution package. During deployment the following error occurs "Cannot add the specified assembly to the global assembly cache". This would probably suggest a lock on the timer service, except that the remote deploy script calls IIS reset/timer reset prior to and after upgrade. Checked the event viewer on remote server and seems that yes, they were in fact successfully called. I'm not using the build definition as part of the starter pack (but I assume the steps would be rather similar). A manual upgrade of the versioned package works and the same upgrade procedure works without the assembly versioning action. Anything I could have missed?