I have just completed the arduous process of integrating ClickOnce deployment (with
the ability to have multiple versions installed side-by-side EX: DEV,QA,UAT) into
my TFS 2010 build script. This took me about a week due to lack of materials
on the web. So for everyone else out there attempting this here is what I did to
make it work.

In order for this to work you must have the MSBUILD community tasks installed on
you build server. You can download these from here msbuildtasks.tigris.org

- The condition statement is reading some out of box and custom MSBUILD properties
that we will define and set when we create our build definition to actually perform
the build/deploy. In the end, this <Import> block will only run if the conditions
are met which will in turn only run the code in out ClickOnceDeployment.targets
file if these conditions are met.

These steps were compiled from many different sources and heavily modified to fit
my specific situation. I know that there are prob places where this can be improved
upon and if you happen to have feedback please leave it in the comments.

Hope that this shortens the amount of time it takes you to get ClickOnce working
with TFS 2010.