Kinook Software Forums

Go Back   Kinook Software Forums > Visual Build Professional > [VBP] Third Party Tools

Thread Tools Rate Thread Display Modes
Old 02-13-2006, 05:35 PM
jkuo jkuo is online now
Registered User
Join Date: 08-23-2004
Posts: 4
.NET solution version stamp

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).


Reply With Quote
Old 02-14-2006, 07:54 AM
kinook kinook is online now
Join Date: 03-06-2001
Location: Colorado
Posts: 5,723
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 for more details.
Reply With Quote

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

All times are GMT -5. The time now is 06:36 PM.

Copyright 1999-2019 Kinook Software, Inc.