ClickOnce installation/signing problem

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?

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.

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.