.NET solution version stamp

[jkuo]

We want our .NET projects to increment their file/product version with each build but the assembly version to stay static throughout the release. So in our build projects, in the Versions tab in the .NET build step, the "Update Assembly version" is unchecked and the file/product versions are set to our dynamic build number.

VBP adds the AssemblyFileVersionAttribute to assemblyinfo.cs for every project in the solution during build. A developer argued that solutioninfo.cs should be the right place for it since there are many projects in a solution and they all carry the same version. What exactly is the right place for this information? Is there anyway we can have it in both places? (currently VBP errs out if it appears in solutioninfo.cs).

Thanks.


Jessie

[kinook]

You can put them in either place. When building a solution or project and specifying version settings, the Make VS.NET action will create/update the related attribute in each project's AssemblyInfo.cs file. Alternatively, if you want to store the version value in a common file, modify the build VS.NET step to not set/increment versions, and create a separate 'no build' Make VS.NET step to update the version value on a specific .cs file. See http://www.visualbuild.com/Manual/vs...olutiontab.htm for more details.