I am looking for a strategy to version an application with the following requirements.My requirements are given an exe with version number (major.minor.build-number)1) I want to map the version to a svn source revision that made the exe2) With the source and exe I should be able to attach and debug in vs2010 with no issue.3) Once I check-out the source code for the exe I should be able to build the exe again with the version number without having to make any changes to a file.
Linking application build number to svn revision
c++;version control;svn;strategy
Side note:While building app from not-modified WC (and, probably, from not-sparse checkout) is human task, you can move task of supporting link to SVNAlternativesUse tags and after creating release (X.Y.Z from revision NNN) in trunk or any branch copy this WC (or repo-tree) to tag X.Y.Z. Later you can always return back to any release by checkout corresponding tagUse custom SVN properties (svn help propset, 1-st type: versioned property) on any always-must-have solution file for storing version-string and change this property (and commit only this change) after release by next commit. In order to find needed revision in this case you have to inspect log of signal-file, find needed revision, checkout found or found-1 revisionPS: Mention of VS means that you can use SubWCRev for getting global repository-wide data on build-stage