How to install SignTool.exe for VS 2017?

2020-07-06 02:19发布

After upgrade to VS 2017 i got "Error An error occurred while signing: SignTool.exe not found." But only using MSbuild on the Visual Studio publish there's no problem.

I already checked folder "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin" and in fact there's no SignTool.exe present. But there was before installing VS2017, any ideas?

I followed this issue but no luck How to install SignTool.exe for Windows 10

6条回答
迷人小祖宗
2楼-- · 2020-07-06 02:38

The all solutions didn't worked for me ; finally i just copied signtool.exe to the project folder and then worked. You can download the signtool.exe from internet or install Windows 10 SDK by visual studio installer and then copy from "C:\Program Files (x86)\Microsoft SDKs\ClickOnce\SignTool".

查看更多
叼着烟拽天下
3楼-- · 2020-07-06 02:43

So the problem I had with this was that the path variable wasn't set up. I ran

set PATH="C:\Program Files (x86)\Microsoft SDKs\ClickOnce\SignTool";%PATH%

in the Developer Command window before trying to sign anything.

If you do it this way you will need to run the set path every time you want to use it unless you add it to the path environment variable. I hope this helps.

查看更多
劫难
4楼-- · 2020-07-06 02:49

C:\Program Files (x86)\Microsoft SDKs\ClickOnce\SignTool> This is where its there in my System.

查看更多
家丑人穷心不美
5楼-- · 2020-07-06 02:56

Signtool is included with the Windows 10 SDK

  1. Open Visual Studio installer.

  2. Switch to the "Individual Components" tab

  3. Choose the version of the SDK that suits your needs.

enter image description here

Multiple copies may be installed.

enter image description here

查看更多
孤傲高冷的网名
6楼-- · 2020-07-06 03:03

Start Developer Command Prompt for VS 2017 then it is in the path variable signtool

That seems to do the trick, now the problem is with setup.bin file.

error MSB3147: Could not find required file 'setup.bin' in csproj folder

查看更多
不美不萌又怎样
7楼-- · 2020-07-06 03:03

I found it under C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin

It could be because it was there before the vs2017 installation.

It doesn't harm to check :)

查看更多
登录 后发表回答