Adding files generated at build time to your ClickOnce deployment

So, it used to be that I didn't really like ClickOnce deployment, but it turns out it has a lot of benefits:

• It provides infrastructure that makes it *exceedingly* easy for your average lay-user to upgrade. All they have to do is start the program as normal, and it automatically updates for them (when configured properly)
• It bundles everything up nicely and is easy to install and uninstall (if you're a real person. If you're a script, not so much)

I recently encountered the problem of including files generated at build time (e.g. transformed configuration files) in the ClickOnce deployment package. I found the following that I could include in my ClickOnce project's .csproj MSBuild file:

 <Content Include="Path\To\My.file" Condition=" Exists('Path\To\My.file') ">
<Visible>false</Visible>
 </Content>

 The key part to getting it to work properly is that your build has to do a Build target first, then a Publish target (usually with two separate invocations of MSBuild via a build script, rather than building with a Solution). Fortunately, I was already set up for that, so getting the extra files included was a dream.

Getting code signing to work with ClickOnce on a TFS Build Agent

Code signing is a giant pain in the butt. You have to :

• Obtain the certificate for signing the code by:
1. buying the certificate from an issuer.
2. generating your own self-signed certificate
• Configure ClickOnce within your project file with the following property elements:
• <signmanifests>true</signmanifes>
• <manifestcertificatethumbprint>A387B95104A9AC19230A123773C7347401CBDC69</manifestcertificatethprint>
• Log into your machine **as the user running the build controller / agents ** and import the key to their user Personal certificate store!
• Run 'certmgr.msc' from the Run command in the start menu (WinKey + R is the hotkey)
• In the Certificate Manager that comes up, go to Personal in the tree, right-click, and select All Tasks -> Import ...
• In the Certificate Import Wizard window that comes up, select Next to move to the 'File To Import' screen.
• Select your certificate file, which has the same thumbprint as specified in your project file, then click Next to move to the 'Certificate Store' screen.
• In the 'Certificate Store' screen, select the 'Place all certificates in the following store' option, then click Browse to select the store. Choose 'Personal' in the selection window. Click Next to move to the "Completing the Certificate Import Wizard" window.
• On the "Completing the Certificate Import Wizard" window that comes up, click Finish to import the certificate.

You should now be able to build and sign your code on a TFS Build controller / agent.