ClickOnce (RSS)

All things related to ClickOnce

CAPICOM error with ClickOnce

Technorati tags: .NET, CAPICOM, ClickOnce

I have a project using ClickOnce for deployment and from time to time, when I want to publish a new version of my application I receive the following error:

SignTool Error: Signtool requires CAPICOM version 2.1.0.1 or higher. Please copy the latest version of CAPICOM.dll into the directory that contains SignTool.exe. If CAPICOM.dll exists, you may not have proper permissions to install CAPICOM.

This problem is happening, because the CAPICOM.dll is not registered correctly and the solution for this is the following:

Copy CAPICOM.dll from Program Files\Common\Microsoft Shared\CAPICOM to the SignTool.exe directory.

I successfully resolved this issue by copying the .dll to this location, but this time no matter what I did I received this error, when I tried to publish. I was pulling my hair, so I decided to check out the deployment option, then after not finding annything there I went to the Signing. I noticed there that I was using a test certificate, what was expired already. Creating a new test certificate solved my problem.

posted Tuesday, April 03, 2007 12:18 AM by gyurisc with 0 Comments

ClickOnce for Orcas

ClickOnce has some new features in Orcas like support for WPF or alternative browser. To me the most interesting one is the ISV rebranding. I think this one lets you to modify the design of the publish.html page. I did a click through all the ClickOnce dialog side by side, but the only thing changed was a new checkbox called Use application manifest for trust information in the Publish Options dialog.

I hope that this will be changing in the next CTPs, because ClickOnce is one of my favorite technologies!

posted Monday, January 29, 2007 2:45 AM by gyurisc with 0 Comments