I am converting a Cruise Control .NET project that uses CVS to one which uses SVN and I am running into a big problem. The current project updates the AssemblyInfo.cs and other version related files with a version based on the label, commits these files, uses msbuild to build the assemblies and executables, and labels/tags the source that went into that build. This all works fine in CVS, but not SVN. The problem I am running into with SVN is that if I change these files and check them in before it runs update, it apparently knows the SVN revision of the code when it started and does an update specific to that revision. This revision does not include the version changes that were made.
If I change the configuration to make the changes and do the commit after the update, then it solves that problem, but when the tag/copy is done it uses a specific revision that does not include these changes. If I change the logic to not commit these changes then the build picks up the correct version but the tag/copy does not include the version changes. If I move the commit to the very end I get the same problem; the wrong version files are in the tag. Does anyone have a good solution to this? John
