Geek Answers Handbook

Signing a VB.NET Application

Do I have to sign my VB.NET applications?

I get an error message:

SignTool reported an error 'Keyset does not exist'

But you have no interest in signing anything, because the project is small and will be used only inside my department.

I can create a temporary key. But why do I want to?

Thanks.

+4
source share
4 answers

The second post here looks like this might help ...

+2
source

I had the same problem ...

I went to the "Signing" tab "My Project", unchecked the box and checked "Sign the ClickOnce manifest," then "Create a test certificate."

I saved and then published. At the time of publication, he asked me to confirm the new certificate. "OK"

It seems to have worked.

+2
source

To answer your first question: no, signing is not required. By default, your projects are not signed.

Perhaps the message Dave will help with your error.

+1
source

Signing an assembly with a strong name usually occurs when the assembly is hosted on the GAC , so a strong name provides a secure binding.

Only the manufacturer of the assembly indicated the public key token , so by making a link to the assembly from your application during development, you can be sure that the same assembly will be used by the user.

So, if your application has a GUI , I think not , signing is not required. If it is a library that can be used publicly, yes , sign it.

+1
source

More articles:


All Articles