Deploying ClickOnce applications automated using FinalBuilder

You may also like...

9 Responses

  1. Dennis van der Stelt says:

    You might run into a problem that the assembly was signed by a different key than the manifest. You’ll get this error:

    “Reference in the manifest does not match the identity of the downloaded assembly xxx.exe”

    The answer can be found here :

    Go to project properties, see the section “Resources” in the application properties and in the icon manifest options, set it to “Create application without a manifest”.

  2. We also use FinalBuilder for building Inbox2, but we simply call visual studio from the command-line to build & deploy the clickonce application.


    Your tutorial does offer a lot more flexibility though 🙂

  3. Diego says:

    Does anybody knows, a tutorial that for FinalBuilder that will automated my built, to change just the version number. For example, I know that my built for my software version 6.0 is working, so I just want to take that built, and just change the version number to 6.1, without going to VS and built the code again.

    Thank you


  4. Dennis van der Stelt says:

    @Diego : You do have to rebuild you code, but isn’t that part of your build already? It should be! First increase the build number in AssemblyInfo.cs, then build the code.

  5. Andrew says:

    This tutorial is great, but I have a particular concern, After I publish my solution from .net, this include create a PA ClickOnce Deployment utility, setup files ready for the client. What can I do with FinalBuilder to take the xtm file, where the version number is, and change the version number, then remove the deploy extension, sign the manifest, and add the deploy extension back. We can do it manually, but we want automatize that process any ideas??

    Therefore the basic question is: How to Change App Version Without Rebuilding?

  6. Rajesh B S says:

    I get this error message

    Following errors were detected during this operation.
    * [11/23/2009 6:05:12 PM] System.Deployment.Application.DeploymentException (ManifestSemanticValidation)
    – The customHostSpecified attribute is not supported for Windows Forms applications.
    – Source: System.Deployment
    – Stack trace:
    at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)

  7. Dennis van der Stelt says:

    @Rajesh : That’s not the entire msg. Contact me via this page ( and we can discuss this offline.

  8. Matt says:

    Awesome article.

    Does Final Builder support generating the boot strapper for prerequisites too?

  9. Alberto says:

    I’m going to try it, but it looks like a bit complicated to do it with finalBuilder, I mean, it feels like I’ll probably will add a step in the build process where it outputs to the console something like this:
    “If there is a problem in the ClickOnce publish or you want to perform a change, please visit the blog: %ThisBlogLink%”, and/or everytime I’ll tell someone hey I simplified how we do ClickOnce, all you have to do is learn how ClickOnce works.

    But thanks for the article, I still need to implement it, I’m going to implement it with continua, in a 2 step process, so I’ll have a FinalBuilderProject to publish any compiled files. and another for each project I may want to build and test.

Click on a tab to select how you'd like to leave your comment

Leave a Reply

Your email address will not be published. Required fields are marked *