I have a VB.Net Visual Studio 2015 project that creates an exe file for people inside the company. We have never had to enter code before, but when our computers switch to Windows 10, we get warnings and warnings from Windows that the EXE does not trust. The idea was brought to the code mark for the application when it was built.
We are currently using the InstallShield installer for the EXE and its files. I have local test certification and private key / public key. At the moment, however, I do not know how to encode the character. I used the Signature tab in the properties and parameters of the project, but this does not sign the actual EXE. At least SignTool does not consider it signed. And we do not want to use ClickOnce for publishing or deployment.
Do I need to do this through the command line? Or is there a place for Visual Studio to label the code?
EDIT: I know I can just write a script message to add code signing, but I would expect Visual Studio to be able to enable this.
source share