AKA the revision number? Also useful.
Brings up another question: Is anyone using symbol server with source
information built into the PDB file?
like this:
http://result42.com/howto/symbol-storage-subversion-indexed-symbols
http://brockreeve.com/post/2009/10/23/Symbol-Server-Setup.aspx
On
Piers
I've always been turned off using TeamCity because of reported problems of
TeamCity with SVN and VisualSVN (I use a licensed copy of VisualSVN with
TortoiseSVN on desktop).
Ian Thomas
Victoria Park, Western Australia
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@o
I'd just use the build number management that your CI server (eg TeamCity)
gives you. That way you can always go back to the build logs if something
looks odd.
On 3 Jul 2013 13:42, "Ian Thomas" wrote:
> I have been using Versioning Controlled Build (VCB v3.x) from a
> CodeProject article for some
Don't use too many version levels - MSI for one doesn't seem to handle them
gracefully. But I store the major minor versions in a text file in SVN,
and use the main build script file to increment and commit the build
number.
Mike
On Wed, Jul 3, 2013 at 3:42 PM, Ian Thomas wrote:
> I have been
I have been using Versioning Controlled Build (VCB v3.x) from a CodeProject
article for some time, with VS2010 and earlier. Do others have preferences
for other simple build version increment / control addins?
Ian Thomas
Victoria Park, Western Australia
