index > ClickOnce and Setup & Deployment Projects > Publish ClickOnce project with Team Build?

Publish ClickOnce project with Team Build?

Does anyone have any examples of how to create a Team Build BuildType that publishes the project similiar to the way you manually do it in visual studio?

I already have the BuildType created and working (it gets kicked off on a schedule). I've also created a BeforeDropBuild task that does GenerateApplicationManifest and GenerateDeploymentManifest that also works. This was a bit confusing -- when the BuildType is run not through the GUI many of the properties don't exist and most of the examples appear to assume they would. Anyway, these steps work in that the build does not fail.

Somehow I need to publish the manifest I suppose, but I can't find any examples of how to do it. I'm not even sure I know the right questions to ask.

Any help would be appreciated.

Thanks!

ongle

Here is a very good article that should cover everything you need

http://blog.gatosoft.com/PermaLink,guid,d0a0dd1e-c9ac-4fa9-a408-615454d49702.aspx

I adapted it for Team build and to use versioning, here is an example:

<?xml version="1.0" encoding="utf-8"?>

<!-- TO EDIT BUILD TYPE DEFINITION

To edit the build type, you will need to edit this file which was generated

by the Create New Build Type wizard. This file is under source control and

needs to be checked out before making any changes.

The file is available at -

$/{TeamProjectName}/TeamBuildTypes/{BuildTypeName}

where you will need to replace TeamProjectName and BuildTypeName with your

Team Project and Build Type name that you created

Checkout the file

1. Open Source Control Explorer by selecting View -> Other Windows -> Source Control Explorer

2. Ensure that your current workspace has a mapping for the $/{TeamProjectName}/TeamBuildTypes folder and

that you have done a "Get Latest Version" on that folder

3. Browse through the folders to {TeamProjectName}->TeamBuildTypes->{BuildTypeName} folder

4. From the list of files available in this folder, right click on TfsBuild.Proj. Select 'Check Out For Edit...'

Make the required changes to the file and save

Checkin the file

1. Right click on the TfsBuild.Proj file selected in Step 3 above and select 'Checkin Pending Changes'

2. Use the pending checkin dialog to save your changes to the source control

Once the file is checked in with the modifications, all future builds using

this build type will use the modified settings

-->

<!-- DESCRIPTION

The description is associated with a build type. Edit the value for making changes.

-->

</Description>

<!-- BUILD MACHINE

Name of the machine which will be used to build the solutions selected.

-->

<BuildMachine>buildmac</BuildMachine>

</ProjectExtensions>

<!-- TEAM PROJECT

The team project which will be built using this build type.

-->

<!-- BUILD DIRECTORY

The directory on the build machine that will be used to build the

selected solutions. The directory must be a local path on the build

machine (e.g. c:\build).

-->

<BuildDirectoryPath>c:\localbuilds</BuildDirectoryPath>

<!-- DROP LOCATION

The location to drop (copy) the built binaries and the log files after

the build is complete. This location has to be a valid UNC path of the

form \\Server\Share. The build machine service account and application

tier account need to have read write permission on this share.

-->

<DropLocation>\\xxx\LocalBuilds</DropLocation>

<!-- TESTING

Set this flag to enable/disable running tests as a post build step.

-->

<RunTest>false</RunTest>

<!-- WorkItemFieldValues

Add/edit key value pairs to set values for fields in the work item created

during the build process. Please make sure the field names are valid

for the work item type being used.

-->

<WorkItemFieldValues>Symptom=build break;Steps To Reproduce=Start the build using Team Build</WorkItemFieldValues>

<!-- CODE ANALYSIS

To change CodeAnalysis behavior edit this value. Valid values for this

can be Default,Always or Never.

Default - To perform code analysis as per the individual project settings

Always - To always perform code analysis irrespective of project settings

Never - To never perform code analysis irrespective of project settings

-->

<RunCodeAnalysis>Never</RunCodeAnalysis>

<!-- UPDATE ASSOCIATED WORK ITEMS

Set this flag to enable/disable updating associated workitems on a successful build

-->

<WorkItemTitle>Build failure in build:</WorkItemTitle>

<DescriptionText>This work item was created by Team Build on a build failure.</DescriptionText>

<BuildlogText>The build log file is at:</BuildlogText>

<ErrorWarningLogText>The errors/warnings log file is at:</ErrorWarningLogText>

</PropertyGroup>

<!-- SOLUTIONS

The path of the solutions to build. To add/delete solutions, edit this

value. For example, to add a solution MySolution.sln, add following line -

To change the order in which the solutions are build, modify the order in

which the solutions appear below.

-->

<!--

-->

</ItemGroup>

<!-- CONFIGURATIONS

The list of configurations to build. To add/delete configurations, edit

this value. For example, to add a new configuration, add following lines -

<FlavorToBuild>Debug</FlavorToBuild>

</ConfigurationToBuild>

The Include attribute value should be unique for each ConfigurationToBuild node.

-->

<FlavorToBuild>Release</FlavorToBuild>

</ConfigurationToBuild>

</ItemGroup>

<!-- TEST ARGUMENTS

If the RunTest is set to true then the following test arguments will be

used to run tests.

To add/delete new testlist or to choose a metadata file (.vsmdi) file, edit this value.

For e.g. to run BVT1 and BVT2 type tests mentioned in the Helloworld.vsmdi file, add the following -

</MetaDataFile>

Where BVT1 and BVT2 are valid test types defined in the HelloWorld.vsmdi file.

MetaDataFile - Full path to test metadata file.

TestList - The test list in the selected metadata file to run.

Please note that you need to specify the vsmdi file relative to $(SolutionRoot)

-->

</MetaDataFile>

</ItemGroup>

<!-- ADDITIONAL REFERENCE PATH

The list of additional reference paths to use while resolving references.

For example,

-->

</ItemGroup>

<PublishDir>$(SolutionRoot)\..\Publish</PublishDir>

<SupportUrl>http://tempuri.org</SupportUrl>

<SigningCert>$(SolutionRoot)\ClickOnce\ClickOnce\ClickOnce_TemporaryKey.pfx</SigningCert>

<Company>Company yyyy</Company>

<ClickOnceAppName>ClickOnce</ClickOnceAppName>

<SourceDir>$(SolutionRoot)\..\Binaries\Release</SourceDir>

<ClickOnceVirtualRootDir>C:\Inetpub\wwwroot\ClickOnce\Dev</ClickOnceVirtualRootDir>

<ClickOnceUrl>http://localhost/ClickOnce/Dev/</ClickOnceUrl>

<ClickOnceApplicationUrl>$(ClickOnceUrl)$(ClickOnceAppName).exe.application</ClickOnceApplicationUrl>

<ClickOnceDescription>The application description</ClickOnceDescription>

<TF>"$(TeamBuildRefPath)\..\tf.exe"</TF>

<AssemblyInfoSpec>AssemblyInfo.cs</AssemblyInfoSpec>

</PropertyGroup>

</ItemGroup>

</ItemGroup>

</ItemGroup>

</ItemGroup>

</Target>

<Output TaskParameter="Assemblies"

ItemName="GetVersionAssemblyInfo"/>

</GetAssemblyIdentity>

</Target>

<Copy SourceFiles="@(SourceFiles)"

DestinationFiles="@(SourceFiles->'$(PublishDir)\%(RecursiveDir)%(Filename)%(Extension)')"/>

<Copy SourceFiles="@(AppConfigFile)"

DestinationFiles="$(PublishDir)\$(ClickOnceAppName).exe.config"/>

<Copy SourceFiles="@(ClickOnceLandingPage)"

DestinationFiles="$(PublishDir)\default.htm"/>

</Target>

</CreateItem>

<ModifyFile