SpiceLogic Inc.
                                                                                                     SpiceLogic Inc. Home PageProductsJournalMy AccountHelp DeskContact Us
 
Knowledge base  : .NET Win HTML Editor Control    - Standard Edition
Welcome Guest   Login

Skip Navigation Links. .NET Win HTML Editor Control

Documentation  Documentation

Download   Download the latest version

Back to the home of knowledgebase forum ClickOnce Deployment Problem

An user   3/21/2009 9:41:41 PM

I’ve just attempted the first installation of my new product, but there was a problem with the “strong signature” of MSHTML.dll, and the entire application would not install. I attach an .rtf file with the details of the attempt. The salient points are shown bold.
 
As you’ll see, there was a warning when publishing the application, and an error when installing it. On my first attempt I signed the ‘ClickOnce manifests'; on my second attempt I signed the ‘ClickOnce manifests' AND ‘the assembly’; on my third attempt I left all checkboxes unmarked in the ‘Signing’ index tab so that the application was unsigned.
 
You’ll see the results of these attempts in the attached file. The first two reports were identical;, so I’ve shown them only once.
 
I remember reading somewhere on your web site that, if there was a problem with the “strong signature” of MSHTML.dll, you could fix it. I’d appreciate a solution as soon as possible, please, as my customers are waiting for my product. Thank you.



An user   3/21/2009 9:43:41 PM

Regarding the COM registration (which is an unknown area for me), I see in my IDE that the ‘Register’ property for the ‘Microsoft.mshtml.dll.deploy’ object has 3 options: “vsdraDoNotRegister” (the default value), “vsdraCOM” and “vsdraCOMRelativePath”. These differ from the article at http://www.simple-talk.com/dotnet/visual-studio/getting-started-with-setup-projects/ in that the values mentioned there are “vsdrfCOMSelfReg”, “vsdrfCOM” and “vsdrfCOMRelativePath”. In my IDE I have changed “vsdraDoNotRegister” to “vsdraCOM”, in the hope that this is correct.




Resolution:
An user   3/21/2009 10:01:16 PM

PROBLEM SOLVED!

I searched on the Web for this problem, and found the solution at 
 
http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/9b5a07e0-bb1f-4f3d-90fc-40777f1f5800/

My project was referencing the “…\PIA\…” copy of ‘mshtml.dll’. When I changed the path to the SpiceLogic copy, everything worked.

Now I am so relieved. Have a good day, and thanks for trying to help!




Home  || Products  || Journal  || My Account  || HelpDesk  || Contact Us

Website and Software Copyright ©2010, SpiceLogic Inc., All Rights Reserved.