asked on

Why wont a signed ClickOnce application not display the Trusted Publisher?

Attached to this question are some pictures to give you guys an idea of what we are doing.

1.

The code is signed with a Verisign Class 3 Code.

2.

It's published through Visual Studio to our Web Server.

3.

When I click on download it displays the warning message.

4.

It doesn't show the Trusted Publisher.
The only thing that I believe might be the issue is that one of the projects references the...
Microsoft.Office.Core
Microsoft.Office.Interop.Word
Microsoft.Vbe.Interop

The weird thing is that when the project is installed those dll's are not included in the project so I guess it's getting it from the GAC.

I did create a simple project and just signed it and it worked fine. But this application is pretty big and removing the Office references would make the program completely un-buildable.

Any suggestions or ideas would be greatly appreciated.

Regards,

RAFF
SignedCode.PNG
publishpage.PNG
DownloadClickOnce.PNG
MoreInfoClickOnce.PNG

SOLUTION

kaufmed

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jjdahl

ASKER

Hi Kaufmed,

Yeah I read that a thousand times, haha. Hard to decipher but I think we have most of that down.

Here is a simple example I made that just says hello world, with clickonce and the certificate.

ClickOnce Hello World Test

You can see that it prompts you with the trusted info.

I'm using the same certificate and timestamp and everything looks good to me. If you don't wish to click the link, I uploaded images of the prompts to give you an idea.

I'm going to start to slowly add parts to it to see which project breaks the trusted publisher section.

Thank you,

RAFF
ClickOnceInstall.jpg
ClickOnceMoreInformation.jpg
ClickOncePublisherInformation.jpg

kaufmed

Well I think the part that is causing you trouble is: "you need to configure the publisher certificate on the machine where the app will be launched with ClickOnce." I know that with regular .NET apps there is some registration with Microsoft that needs to be done in order to prevent such dialogs; perhaps with ClickOnce it is the same. Unfortunately, I found ClickOnce to be more of a pain than a blessing, and I moved away from it a while ago, so I can't really offer any deeper insight.

jjdahl

ASKER

I read about the Microsoft registration part in some sites as well. Maybe I will look into that. Thanks for trying to help. =D

ASKER CERTIFIED SOLUTION

jjdahl

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jjdahl

ASKER

It solved my problem.