After much frustration, I've finally configured our TeamBuild proj file to publish our ClickOnce app, and increase the version number (kinda an important step). The Vertigo blog talks about using SolutionToPublish, but that doesn't work for all situations. Specifically, when your solution contains projects that reference other projects.
So I started playing with the MSBuild Community Tasks Project, and came up with the following Xml for my proj file:
This tells the .proj to use the community project:
<Import Project="$(MSBuildExtensionsPath)\MSBuildCommunityTasks\
MSBuild.Community.Tasks.Targets"/>
This defines the version numbers:
<PropertyGroup>
<Major>4</Major>
<Minor>0</Minor>
<Build>0</Build>
<Revision>0</Revision>
</PropertyGroup>
This sets the Revision to the last Changeset in our TFS server, and sets the Build to a formatted date:
<Target Name="Version">
<TfsVersion LocalPath="$(SolutionRoot)">
<Output TaskParameter="Changeset" PropertyName="Revision"/>
</TfsVersion>
<Time Format="MMdd">
<Output TaskParameter="FormattedTime" PropertyName="Build" />
</Time>
</Target>
This tells TeamBuild to Publish this after the solution is compiled and after the Version code has been ran. It publishes the ClickOnce project to the location PublishDir with the version set in ApplicationVersion:
<Target Name="AfterCompile" DependsOnTargets="Version">
<MSBuild Projects="$(SolutionRoot)\dev\...\ParaPlan.csproj"
Properties="PublishDir=\\server\drop\;ApplicationVersion=$(Major).$(Minor).$(Build).$(Revision)"
Targets="Publish" />
</Target>
The entire .proj file is here.