Unknown Publisher

[MrMancunian]

Hi,

I've created an application with VS2005, but now I want my own name to be shown as publisher (see screenshot).

How do I set the publisher for my application in VS2005?

Thnx,

Steven

[joedeene]

Hi,

I've created an application with VS2005, but now I want my own name to be shown as publisher (see screenshot).

How do I set the publisher for my application in VS2005?

Thnx,

Steven

Go to and click on this Project -> {project name} Properties

Click on the 'Publish' tab on the left side(in a column).

There's an 'Options' button click on that and there are options you can edit for your project.

joedeene

[MrMancunian]

Hi, thanks for your reply. I already tried that, and it doesn't work. Any other suggestion?

Thnx,

Steven

[Curtis Rutland]

It has something to do with digitally signing your apps....I can't find the information on how to do that right now, but I am looking.

[MrMancunian]

It has something to do with digitally signing your apps....I can't find the information on how to do that right now, but I am looking.

Ok, I'll be waiting for it :-)

[MrMancunian]

Has anyone already got any thoughts on this one?

Thanks,

Steven

[Frinavale]

Have you seen this article?

There is a paragraph in there that states:

...By signing a binary, you can add information about the publisher and make sure the signed file can be reliably validated after it has been signed. You can use the signtool.exe tool from the .NET Framework SDK to sign .exe and .dll files. Afterwards, you can verify the signature and view the certificate using the properties dialog in Windows Explorer. Note that if both Authenticode and strong name signatures are going to be used, the strong name signature needs to be applied first. Additionally, Authenticode signed assemblies can experience delays at load time, which translates to a longer application startup time if it's the entry point executable that's been signed.
Signed files can also be used for security policies. Using software restriction policies, you can restrict execution of unmanaged executables based on signatures or the absence of signatures (see microsoft.com/technet/prodtechnol/winxppro/maintain/rstrplcy.mspx). And the .NET Framework code access security (CAS) policy supports code groups based on a publisher certificate.
To create a CAS policy, you use mscorcfg.msc to create a new code group based on a publisher membership condition. You can then assign a permission set to all applications signed by that publisher

-Frinny

[MrMancunian]

Have you seen this article?

There is a paragraph in there that states:


-Frinny

I'll look into it, thanks :-)

Steven