Thanks for all the leads links and advice. Julijan Sribar's code and application at CodeProject was good for me, and the idea of adding a link to projects, to allow synchronized version incrementing in multi-project solutions is great.
And I liked the Albacore vs Nant rants (but I don't use either). _____ Ian Thomas Victoria Park, Western Australia _____ From: [email protected] [mailto:[email protected]] On Behalf Of Heinrich Breedt Sent: Saturday, March 19, 2011 7:23 AM To: ozDotNet Subject: Re: VS version increment problems http://www.lostechies.com/blogs/derickbailey/archive/2009/09/29/albacore-ass emblyinfo-task-vs-nant-assembly-info-generator.aspx On Sat, Mar 19, 2011 at 7:37 AM, Greg Keogh <[email protected]> wrote: I'm using a Shared file between each project (Add Existing item, and make it a link). Then i have this in that shared file [assembly: AssemblyVersionAttribute("2.8.*")] [assembly: AssemblyFileVersion("2.8.0.0")] ...and remove the one in the AssemblyInfo.cs I also use this technique for all multi-project solutions, and I highly recommend it. Put all common assembly attributes in a shared file and link to it from each project. Leave only project specific stuff (Description, Product, Title, Guid) in each project. I first saw this done many years ago in one of the EntLib source releases and I really liked the idea. Greg -- Heinrich Breedt "Do not wait to strike till the iron is hot; but make it hot by striking." - William B. Sprague
