Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    ClickOnce installation/signing problem

    Scheduled Pinned Locked Moved Support
    netclickoncebuildmaster
    3 Posts 1 Posters 38 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Version 3.2.2 (Build 23)

      I am trying to get ClickOnce published application using your MiniCalculator example, but it just doesn't work out of the box.

      First of all, by default it can't find MiniCalc.pfx, so it doesn't sign anything (mage.exe says "File not found - "MiniCalc.pfx"), and I get the following error if I try to install the application:


      • Application manifest has either a different computed hash than the one specified or no hash specified at all.
      • File, MiniCalc.exe.manifest, has a different computed hash than specified in manifest.

      Second, if I specify just certificate hash without certificate's name and password (both fields are empty and the check box is unchecked), then mage.exe generates "Out of range exception".

      Third, if I specify local certificate path (created manually from VS) and password, then mage.exe finally says "MiniCalc.exe.manifest successfully signed" but installation of the application still fails with the same error (see above).

      Am I missing something simple?
      Are you planning to improve ClickOnce expirience?

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        We believe we have found the cause of one of the bugs you are experiencing, it has mainly to do with the default directories in the example itself, where the build output from MSBuild is using the same directory as the source, thus overwriting the source files (including the PFX file), and therefore mage.exe can't find it.

        We will be releasing a new version of the DotNetRecipes extension that should resolve this issue within the next hour.

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          FYI we have released a new version of the DotNetRecipes extension, if you update that extension within BuildMaster then re-create the example app, the signing should work correctly.

          As for the certificate hash problem, that has been resolved in the .NET extension which is scheduled for a release later today or early tomorrow.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation