Dominick Baier wrote:
> The publisher name comes from the certificate with which you sign the ClickOnce
> manifest - you need a proper cert (either via makecert or a CA) with an intended
> purpose of "Code Signing". Then select this cert in the VS signing dialog
> (from store/from file button). This has NOTHING to do with strong names.
>
> dominick
>

> I use Visual Studio 2005 to publish software to clients. The end
> result I need is to simply put our business' name in the dialog box
> when someone installs our software.
>
> I have googled this to no end and have not found a solution that
> works.
> I have tried to use makecert.exe and then pvk2pfx.exe to make a .pfx
> file to use to sign our app, but, one of the .dll's is not strong
> named
> and cannot be renamed. I have tried to use SN.exe -Vr ***, but, that
> doesnt work, b/c the .dll doesn't pass the strong name check. I have
> also tried tlbimp.exe, but, it is not a COM Interop Assembly.
>
> If anyone has any ideas on how to get our name on that dialog box with
> a weakly-named assembly, I would truly appreciate it.
>
> Thanks,
>
> Andrew
>

> Dominick Baier wrote:
>
>> The publisher name comes from the certificate with which you sign the
>> ClickOnce
>> manifest - you need a proper cert (either via makecert or a CA) with
>> an intended
>> purpose of "Code Signing". Then select this cert in the VS signing
>> dialog
>> (from store/from file button). This has NOTHING to do with strong
>> names.
>> dominick
>>
> I have created the certificate, imported it into the trusted Root,
> selected the cert from the store/from file button, and then
> re-published. This gives the same result - 'Unknown Publisher' from
> the client's perspective. One step of yours that I am missing is
> assigning the intended purpose of "Code Signing" - how is that done
> with makecert.exe?
>
> Thanks,
>
> Andrew
>