Auto Incrementing your TeamBuild ClickOnce Deployed Application

My.RAM.Serialize() - TeamBuild ClickOnce – Auto Incrementing Your Version Information

"Using AssemblyInfoTask within your TFSBuild.proj file, you can set your builds to automatically increment your AssemblyVersion and AssemblyFileVersion.  You can also keep your application’s Publish Version in sync, which is useful if you’re publishing your application via ClickOnce. 

The Publish Version is important because that’s what ClickOnce looks at to see if there’s a new version available when the user runs the application.  Updating the AssemblyVersion or AssemblyFileVersion doesn’t tell ClickOnce that there’s a new version of your application to download.

There are a ton of blog posts like this one that tell you how to check in/out files from your TFS so I won’t repeat those steps.  The actual version updates happen inside the <AssemblyInfo> task:

..."

Peter has done it again. He's taken a general direction, "We need a automated nightly build, with auto-ClickOnce deployment, that also auto-increments the revision and published version numbers" and turned it into reality.

It is VERY cool to have a working continuous integration process. To have a nightly build process where every morning we launch our ClickOnce app and automatically get the new nightly built version. It makes check-in fun and yet a little scary too... LOL

 

BTW, If you're interested in following a front line developer through his (and our) TeamBuild and other development adventures, you should check out Peter's blog. He's a content blogger, providing a look into solving real world development problems...

 

Related Past Post XRef:
Auto Increment Build Numbers when using TFS & TeamBuild
MSBuild Community Tasks Project
Auto Increment Visual Studio 2005 Version Build and Revision via MSBuild Task