Hello all,
As i had to both work with msbuild and being bored to not be able to link SVN versions of DoL and builds, i introduced in the SVN a client side versionning.
this i not perfect. Like we are not using a CIS, the revision injection is handled locally, just before the build, not during the commit into the repository.
This 'll ensure the commit is correctly versionned at the compilation, so all in game display of revision will be matching the SVN revision.
I'm totally aware of theis limitation but i don't plan to set up a CIS. This 'll be used mainly for Storm actually, and our self made build server.
If you don't own msbuild community tasks assembly or subversion client, this is simply ignored. Same if your project is not under version control.
This is also bringing another annoyance: as the assemblyinfo.cs is modified, this is triggering a build for all projects in the solution. Well. Think to compile only the part you are changing if possible. Some way to handle this via msbuild are possibles (reading revision and update only if different) but it involves to code a new msbuild tasks - which implies a strong dependency with msbuild community tasks assembly, that we 'll be forced to ship.
Voila, the sunday's talk is over