Bill suggested using the asminfo task to generate AssemblyInfo files at build time. That is exactly what we do and it works great. We source control the file that stores the version number. When it is time to make a build, we - check out the version number for the particular project from source control - use <version> task to increment build number, which updates version number file - get source code and label with temporary label - use version number to fill in fields in assemblyInfo files. - build
If build succeeds, - check in the version number file, which saves a record of the build number. - use the version number to label all files used in this build (rename the temporary label) If it fails, - we "uncheckout" the version file, reverting it back to pre-build state - remove the temporary label so the failed build is not labeled. We use Team Coherence for source control, using custom NANT tasks supporting all of these operations. If I wanted to get fancy, I could have queried Team Coherence for the last successful build label, and used that as an input for <version>, but this works great with no additional code written. Stephen Lewis Envisionering LLC 1982 Innerbelt Business Center Dr. St. Louis MO 63114 (314) 429 7367 x112 [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
