While I was trying to Update my Project I was making - I got an error for the first time I've seen:
'An error occurred while signing: SignTool.exe not found.'
I've never seen this before, So I looked up that SignTool.exe is what signs my project for ClickOnce Deployment.
I also read that is it a part of Windows SDK - but when I looked to find where SignTool.exe is - I saw it right there!
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin
I saw no problem, and I've always published my Project all the time - I'm on Version 68. But this is the first time I've seen this - I didn't touch any options that would do this.
Any help?
ClickOnce Publishing Tools are not installed as part of the Typical Installation Options. So you have to install it in advanced mode.
This dialog can be found in Windows 7 by going to Control Panel > Uninstall a program, right-clicking on Microsoft Visual Studio Professional 2015 and selecting Change. A Visual Studio dialog will open up. Select Modify from the set of buttons at the bottom and the above dialog will appear.
Please Click Once application --> Properties --> Signing -> Unchecked the Sign the ClickOnce manifests.
Problem will be solved.
Note: Be aware that this solution removes security from your project. Seek assitance from a more learned colleague before doing so.
SignTool is moved to another location in the last SDK: C:\Program Files (x86)\Windows Kits\8.1\bin\x86
Need to install ClickOnce Publishing Tools during Visual Studio 2015 setup.
You can re-run the Installation from the Programs and Features section; find Visual Studio in the list and click Change.
You can fix this by clicking on installation application of VS. Then click Modify > Mark ClickOnce App and then upgrade your VS. Also i think #Alex Erygin is right. It is a bad solution to Click Once application --> Properties --> Signing -> Uncheck Sign the ClickOnce manifests. This is not a solution. It only circumambulated the problem.
This is a simple fix. Open the project you are getting this error on. Click "Project" at the top. Then click " Properties" ( Will be the name of the opened project) then click "Security" then uncheck "Enable ClickOnce security settings."
That should fix everything.
Click "Project" at the top. Then click " Properties" -> Signing -> Unchecked [Sign the ClickOnce manifests] is now working
Now try to publish the ClickOnce application. If you still find the same issue, please check if you installed the Microsoft .NET Framework 4.5 Developer Preview on the system. The Microsoft .NET Framework 4.5 Developer Preview is a prerelease version of the .NET Framework, and should not be used in production scenarios. It is an in-place update to the .NET Framework 4. You would need to uninstall this prerelease product from ARP.
https://blogs.msdn.microsoft.com/vsnetsetup/2013/11/18/an-error-occurred-while-signing-signtool-exe-not-found/
Lastly you might want to install the customer preview instead of being on the developer preview
None of the answers above talk about disabling ClickOnce. In my situation, I never used ClickOnce for my applications but after I upgraded to VS 2015 it was suddenly enabled and I got the 'SignTool.exe not found' error when I tried to compile.
To disable you go into the properties of your Project (right click) and choose Security | Uncheck Enable ClickOnce security settings.
You can leave the manifest checked in the Signing tab because it has nothing to sign if it's been disabled.
I've confirmed that unchecking the security resolved the compile error on my projects.
I needed Signing hence couldn't un-check as suggested.
Then goto Control Panel -> Programs and Features -> Microsoft Visual Studio 2015 Click Change then the installer will load and you need to click Modify to add ClickOnce Publishing Tools feature.
I did have similar problem. For some reason under
project properties -> Signing -> Sign ClickOnce manifests was enabled.
I unchecked it and the problem went away.
Reinstalling SDK did not help me but installing SDK+.NET 3.5 did from link below:
https://www.microsoft.com/en-us/download/details.aspx?id=3138
Windows 10 users can find signtool.exe in C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64 folder (10.0.18362.0 in my case, or other version).
But first, make sure you've installed Windows 10 SDK
Then, check Windows SDK Signing Tools for Desktop Apps is installed by going to Control Panel > Programs > Programs and Features, choose Windows Software Development Kit - Windows 10.0.18362.1 (in my case, you version may be different), right-click, choose Change, choose options Change then click Next.
I had the same issue/error message just after upgrading Visual Studio Pro 2019 V16.6.0. Solution was to make sure that the signing certificate is valid as mine had expired by a day.
Look in properties and signing to either enter a valid or temporary certificate. To keep the file name the same as before then un-click the security as mentioned above and then delete the key file linked to the programme.
Create a new key file and then add back the security.
Solution Explorer
Your app Right Clik
Propatis
Security
Unchek (Enable ClickOnce Security Settings)
Thats Solve..... __:)
https://i.stack.imgur.com/62nKZ.png See
[enter image description here]
After upgrading build tools in DevOps build agent to visual studio 2019, we started getting the below error for 64-bit build step of a WPF application.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(3975,5): error MSB3482: An error occurred while signing: SignTool.exe was not found at path
I tried all the above answers except the ones to disable signing or signing security and nothing helped.
Disabled the default MSBUILD step
Added a cmd prompt step
The path is
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MsBuild.exe"
Note: Removed amd64 from the path above.
This is still a workaround. I hope Microsoft will fix it in the following release.
For VS 2019 or later (Windows 11)
Option 1 (Recommended) -
ClickOnce Publishing Tools are not installed basic Installation. Therefore you will have to manually check and install.
Go to Visual Studio Installer
Then Click modify
Finally, select Individual components tab, search for ClickOnce Publishing and install
Restart the computer.
Option 2 (Not recommended) -
Click Once application --> Properties --> Signing -> Uncheck Sign the ClickOnce manifests. This is not a solution. A workaround.
Option 3 -
Install Windows 10 SDK. Check Control Panel > Programs > Programs and Features > Windows Software Development Kit
Related
Each time I open Visual Studio Community 2017, I get the dialog below asking about upgrading the version of Microsoft Azure Tools.
This dialog appears 4 times (4 different projects), I click 'OK' each time and then everything seems to work fine. However, next time I open the solution I have to repeat the process.
How do I resolve this once and for all?
Note that this project was created under a different version of VS (likely with a different Azure Tools) but that shouldn't be a permanent issue, I'd think.
That's strange...
Have you tried upgrading the project this way:
In Solution Explorer, open the shortcut menu for the project node, choose Properties, and then choose the Application tab of the dialog box that appears
The Application tab shows the tools version that’s associated with the project. If the current version of Azure Tools appears, the project has already been upgraded. If you've installed a newer version of the tools than what the tab shows, an Upgrade button appears.
This may help as well: https://learn.microsoft.com/en-us/azure/vs-azure-tools-upgrade-projects-to-the-current-version-of-the-azure-tools
I'm running Visual Studio 2012, when I add a new File/Reference to a project the message box appears showing the error message
set property 'system.windows.resourcedictionary.deferrablecontent' threw an exception
I read an MSDN article suggesting to run the command devenv /resetuserdata on visual studio command prompt to resolve this problem, tried it but didn't work for me. In fact the command prompt shows the Unknown Error message.
Some addins cause this issue for me so have had to workaround it whenever it occurs:
In Vis studio -
Tools > Options > Environment > Add-in Security, uncheck 'Allow Add-in components to load', OK
Restart vis studio
The error shouldn't occur anymore, so go back to
Tools > Options > Environment > Add-in Security and re-check Allow Add-in components to load, OK
To be specific, I get this error when trying to add files to projects and manage Nuget Packages.
Update
I now make a point of opening
'Tools > Nuget package manager > Manage nuget packages for solution'
whenever I open up a new instance of Vis studio, before loading a solution, just to make sure the window loads properly
That way I know I won't get this issue.
In my case it was a style with the same key defined twice in a ResourceDictionary (WPF)
I have Windows azure tools for Microsoft VisulStudio 2013- v2.2 and Windows azure tools for Microsoft lightswitch VisulStudio 2013- v2.2.
I uninstall only Windows azure tools for microsoft lightswitch vs 2013 .
It's working fine...
I fixed it. The resolution was to remove the Windows Azure Tools for Visual Studio 2012 which I was not actually using, and the error went straight away.
In my case it was to first launch Visual Studio in safe mode. You can create a shortcut for visual studio with a target like this:
'"F:\Program Files\Visual Studio\VS2013\Common7\IDE\devenv.exe" -safemode'
Once launched in safe mode, you can remove the problematic extension via the Addin Manager. However, this wont work for some extensions, as the uninstall option might be disabled for certain extensions when running in safe mode, particularly if you have already uninstalled another extension in the same session.
In My case the problem was caused by Paradox Game engine, in which I had uninstalled it via 'Programs and Features' - which in return did not remove the extension which was originally installed via Nuget package. Uninstalling Paradox via "Programs And Features" left the extension itself still registered in Visual Studio, presumably causing a hidden NullReferenceException.
This issue can be caused by any extension that may have an error in it, or by extensions that were not properly uninstalled.
Also, see this article...
The mentioned issue can be resolved by simply restart the Visual Studio. :P
Also seem to be able to get around this by closing the project and vis studio instance, re-opening, then when the start page/open project screen appears selecting Tools > Extensions and Updates..., then pressing Close
Now open the project and the error doesn't get thrown when trying add files or manage nuget packages, weird.
Just annoying you have to remember to open Extensions and Updates each time...
Other wise make sure given Resourcedictionary.xaml path is correct or not
I had to remove Xamarin from Add/Remove Programs in Control panel and restart Visual studio to fix this.
I had this problem with My Devexpress Project in VS 2015
What finally worked for me was.
Close my solution,
Close Visual Studio,
Open Visual Studio,
Create a New dummy project,
Add a form to it,
Close and save the new project,
Reopen original project and all was ok.
for everyone else who are working in silverlight sdk environment with windows phone8 sdk.
The versions of sliverlight which are compatible with visual studio versions -
vs2012- sliverlight sdk 4
vs2013- silverlight sdk 5
I was integrating in vs2013 and as soon as I updated it with silverlight sdk 5, The errors went away.
In my case it was the Line Endings: you can have different formatting and by copy pasting some code one file got a different Line Ending. It was enough to File > Save As and then click the little arrow next to the save button.
Then click on save with encoding and choose the one you are using in all other files.
See Andrew Truckle's answer.
I hope this helps
Issue
I have a .net 4.0 Web Application running in visual studio 2012, every time I go to debug the site i'm receiving the following error:
The Web Server Could Not Find the Requested Resource
What I've tried
I've followed microsoft's website with solutions: msdn
From a command prompt window, run the following command: systemroot\Microsoft.NET\Framework\ versionNumber \aspnet_regiis -i
I've also attempted to remove the .csproj.user files
Since we use Source Control i've deleted all items, the site and apppool and reconfigured from scratch.
AppPool is set to allow 32-bit applications
All to no avail...Anyone have a solution that might solve this visual studio debugging nightmare for me?
Steps:
Close all solutions in Visual Studio
open IIS7 (run > inetmgr)
Click your top node (computer name)
Open the "ISAPI and CGI Restrictions" option
check if your .Net version has the correct restriction (for example, if you're working with 4.0 is should be on "Allowed")
I was getting the same error when i was running the ASP.NET project from the IIS. I resolved this issue by configuring IIS.
Go to run
type appwiz.cpl and press enter.
Look for "Turn windows features on or off" and click on it
now windows will open for Turn windows features on or off
look for Internet Information service and select that option.
go to world wide web service under the Internet Information service branch
expand Application development feature
Select all the ASP and .net version. and click on OK.
now try running the application from asp.net , it will work :)
I had the same symptoms but a completely different problem. I had attempted to install Url Scan and it didn't seem to work correctly as I could not find the .ini file to edit settings within. I had forgotten that I had installed it, but it appears by default it will prevent debugging from working.
Uninstalling Url Scan solved the issue for me. To uninstall it I had to right-click on the .msi file and choose Uninstall. Url Scan did not show up under the "Add or remove programs" section.
I have downloaded and installed Microsoft Visual Studio 2010 Express for Windows 7 Phone. Problem is that i cant see "Silverlight for Windows Phone" option when I right click my Project name and select Add -> New Item option. I can only see "XNA Game Studio 4.0" under "Visual C#" category.
I have tried installing Silverlight SDK separately by downloading it from Microsoft site but the installer tells me that i have already installed the newer version of the SDK. Due to this problem I can't use few Silverlight classes like ChildWindow etc.
Can anyone please help me in this regard?
I personally haven't had problems with the WP tools install, but I have witnessed others having problems. The only advice I can give is to uninstall all the tools, sdk, etc and reinstall with the latest.
It's a pain, but might be necessary unless someone has a better idea.
The instructions at http://msdn.microsoft.com/en-us/library/ff402526(v=VS.92).aspx say
Make sure you have downloaded and installed the Windows Phone Developer Tools from the App Hub.
So my advice is to make sure you've done that.
Right having just struggled with this myself I finally found an answer.
If you have a Full version of Visual Studio installed it will not install the templates to the Phone version of C# express (turns out it is actually a different executable to the standard C# Express, go figure)
So to resolve this you need to do a couple of things:
Snippets
First, add the path to the Snippets in the snippet Manager using "Tools -> Code Snippets Manager"
Click on "Add" and enter the following Path:
C:\Program Files (x86)\Laurent Bugnion (GalaSoft)\Mvvm Light Toolkit\Snippets\CSharp\
(Note ignore the (x86) if you are on a 32bit system)
This will install the installed snippets into VS Express.
Templates
Now this is a little more tricky but bear with me
Copy the MVVM folder from:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates\CSharp\Silverlight\
To
{Documents Folder}\Visual Studio 2010\Templates\ProjectTemplates\Visual C#\
(Replacing the {Documents Folder} section with your My Documents folder)
Repeat the above replacing ProjectTemplates with ItemTemplates
Finally!!
To finish this off you have to tell VS Phone Express to actually install the templates
Run a Command Prompt with administrative privileges (either create a command line short-cut on the desktop and right-click run it with admin privileges or use the VS tools command prompt)
Run the Following command in that window
"c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\VPDExpress.exe" /installvstemplates
(Note ignore the (x86) if you are on a 32bit system)
If all goes well you should see nothing happen :D, but if you run VS Express for Windows Phone now you will have the new templates installed and the item templates plus the all useful code snippets
Hope this helps!
How might I go about creating an application that does not need that "Publisher Cannot be verified" window?
How can I get my Windows Forms application in a EXE file so that I can just click it and it runs, not asking me to do anything? Maybe this can be done by disabling ClickOnce, but how can you do that in Visual Studio 2010 Express?
I think the reason that no one understood your question is that the only time ClickOnce is used for deployment is when you use the "Publish" wizard.
What you're looking to do is: Go to the Build menu -> Configuration Manager -> and change the "Active solution configuration" to release. This will make Visual Studio optimise your code. Then F6 (Build Solution) and your basic exectutable (.exe) files will be in your {projectDirectory}/bin/Release folder, and you'll be able to run this from any computer that has the .NET framework you compiled in.
Using ClickOnce involves opening a link in a browser that ends in ".application", but it sounds like you're just launching a normal EXE from your local machine, so I don't think ClickOnce is involved.
Did you copy the file to your machine across a network? Right-click on the EXE, open Properties, and see if there's an "Unblock" button at the bottom of the window. If so, click it.
The "publisher cannot be verified" message relates to code signing. Like I said above, you should be able to tell Windows not to be so strict with that file, but if you really need to get signed, you could start with MSDN's Introduction to Code Signing.
The message occurs because the certificate used to sign the ClickOnce XML site can not be verified. These MSDN articles describes the problem:
How to: Get Rid of the Publisher Cannot Be Verified Alert When Taking External Lists Offline
Trusted Application Deployment Overview
Are you using ClickOnce deployment? You can not get rid of the "Unknown publisher" window unless you have a valid certificate with a trusted publisher, and you install it on the user's machine.