When I try to publish a project, the error shows:
Error 2. SignTool.exe Missing.
I searched on my computer for SignTool.exe, the file doesn't exist.
I installed the Windows SDK, that didnt work, the file still doesn't exist. Then I installed the .Net framework, Silverlight, then reinstalled the whole Microsoft Visual Basic.
The file still doesn't exist.
Where can i download SignTool.exe?
signtool.exe is part of the .NET SDK. You'll need to download that, which will install it into the proper location.
You should be able to find the .NET SDK with a search on MSDN. There's no point in posting a link here, because they change over time or as new versions are released. (You can also find it by searching Google for "dot net sdk", which returns many different links to the Microsoft pages.)
I had the same issue but installing the Windows SDK did not work for me (signtool.exe was still missing from my machine).
I stumbled across this solution: http://www.benedykt.net/2015/08/12/missing-signtool-exe-w-visual-studio-2015/
Basically:
Open Programs and Features
Select 'Microsoft Visual Studio [version]' and click Change
And select 'ClickOnce Publishing Tools' for installation
Related
I have been using Visual Studio 2010 Pro for my vb.net desktop application development. I publish the apps via clickonce to a web server with ftp. My settings look like this:
Publishing folder location: ftp://www.webaddress.com/folder/
Installation folder : http://webaddress.com/folder/
This works perfect in VS2010.
I am now trying to upgrade to Visual Studio 2015 community edition. When I try to publish my app, I get the error "The components for communicating with FTP servers are not installed". I am getting this error on both computers I have installed VS2015 on.
Strangely enough, there isn't much info on this error. The only solution I've seen is to repair the installation. I did this but still a no go.. Another cause I read about is having Xamarin installed, but I have never had that installed.
Has anybody run into this and know what the fix is??
EDIT:
It appears to not actually have anything to do with installed components. After I posted this question, I realized the publish via FTP had worked earlier on a little sample Hello World project i made (brain fart). It was only once I loaded my existing project that this error started showing up.
I closed the solution, created another simple project, and still got the error. I closed visual studio, reopened the sample project, and ftp worked! I then opened my existing project and ftp worked there too?! So I don't know what the trigger is, and I haven't had it fail again yet, but maybe this info will help figure out what is causing the failure.
EDIT (3/30/2017)
Just an update - I am still having this issue. This issue happens on visual studio 2013, 2015, and 2017. I have tried reinstalling the c++ redistributable, still nothing. It seems others are having this issue with a web project but mine is a desktop app publishing with clickonce via FTP. It must be something to do with solution I am working on that was originally created in 2010, as the issue is not present in any other project.
I had the same issue with Visual Studio 2017. What fixed it for me was to start the Visual Studio Installer and install the ".NET Core cross-platform development" workload.
I had the same issue in Visual Studio 2015 / Update 3. It was resolved after installing the 32-bit version of Visual C++ Redistributable Packages for Visual Studio 2013 (https://www.microsoft.com/en-us/download/details.aspx?id=40784)
See also https://github.com/aspnet/Tooling/issues/748
I had the same problem with Visual Studio 2015. And Publish used to work fine so I went going crazy looking for and trying different solutions. Then I read on another thread of doing a Setup-> Repair (submitted by Erikest). I did a Setup->Repair and the publish process now works! I think it's also possible that the Repair not only did the trick on the FTP components but also replaced the C++ redistributable (often mentioned as a solution to this problem),
This is a total work around, but I've noticed I get this error every time I open my app (that originated in VS2010) and try to publish without first opening a sample app. I created a new project and published it to my FTP server. When I receive this error, I close Visual studio, reopen and the open the sample project, publish that app, then open my real app. The publish then works.
This works every time, and seems to be a bug in Visual studio, and probably has something to do with the fact that my app was originally built in 2010.
Maybe this will help somebody else with the same issue. It's a big pain so hopefully MS gets a fix in for this.
I have been banging my head against this problem for many months, re-installed VS over and over and just did a clean install of Windows 10 in the hope it would work but to no avail. By chance I cleaned some old .accdb files from the App_Data folder that I no longer need since I converted to SQL Server database and FTP publishing now works.
So it seems VS does not like the .accdb files but was happy with .mdb files when publishing with FTP.
As soon as I put the file back in App_Data the problem returns. Hope this is some help.
I had the same issue here, I was using the Publish right click option on the project, which had been working fine. What fixed it for me was going back through the publish options and re-testing the connection. Publish seemed to work after that. Maybe it forgot a password or settings?
I also installed the x86 C++ Redistribution Package.
Hope this helps someone who is in the same boat.
After many successful website publishes with Visual Studio 2015 Community Edition, we experienced the "components for communicating with ftp servers are not installed" issue. :(
First attempt at resolution was uninstalling VS Community 2015, then installing VS Community 2017. Received the same error: "components for communicating with ftp servers are not installed" when attempting to publish our business website.
With some work, we found that by uninstalling Microsoft Web Deploy and re-installing, this seemed to fix the problem. We can now use Visual Studio > Publish function to our ftp without problems.
See this link for download of Microsoft Web Deploy components.
https://www.microsoft.com/en-us/download/details.aspx?id=43717
Dont know what broke this VS IDE functionality, but hope this fix helps some.
I encountered the same error with Visual Studio 2019
I fixed it by using the Visual Studio Installer to install the Web Deploy (inc .netcore 2.1) under individual components
I just did a simple "repair installation" in the installer. Worked for me.
I am using Microsoft Visual Studio Community 2019 and had this problem for a while.
The problem went away after I updated about 10 NuGet updates that were over due.
I had the same problem, I closed all the open windows I closed Visual Studio and then I opened again and published and then it worked!
I have a Win10 clean install with VS2015 installed. I have Office 2010 for Home and Student. My VB.NET app's msi file was built in 2011 on a machine with Office 2000 installed, and it still works now to install my app in Win10. The installed app exports data to Excel and that still works.
Now I want to update the app with VS2015, but I get build errors, e.g.: Type 'Excel.Workbook' is not defined. I found out that I should load the Office Interop Assemblies.
I downloaded and ran o2010pia.msi, but nothing showed up in "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Visual Studio Tools for Office" where I think they should live. Possibly the installation code is not yet recognizing VS2015 as Visual Studio 14.0?
In searching for answers, I found references to "PIAs in the GAC" and "reference a local copy of the PIAs in your source control tree". But I don't know what these mean!
How can I fix this?
I also missing Microsoft.Office.Interop.Excel.dll after installing Win10.
I find it in
"C:\Windows\assembly\GAC_MSIL\Microsoft.Office.Interop.Excel\15.0.0.0__71e9bce111e9429c".
Maybe you can search it in C:\Windows\assembly.
I found a solution to my problem. I had spent days googling around for answers about missing PIAs and error messages about .NET 3.5 not found. I tried many suggested workarounds, but none worked for me. But...
Because I have ReSharper from JetBrains installed, I stumbled upon this from a left-click on my project folder which shows a context menu with this link: "Optimize References..."
So as an experiment, I clicked it. It ran and did whatever it does (besides reporting). I did nothing! Now my project builds, runs, and automates Office Excel just like it did before my Windows 10 and VS2015 upgrade.
Here's a reference: http://blog.jetbrains.com/dotnet/2012/01/03/optimizing-assembly-references-with-resharper-61/. Hope this helps somebody.
Just had the same issue after an upgrade from Windows 7 to 10. I resolved it by bringing up the references, writing down the path to the Microsoft.Office.Interopt.Excel.dll, removing the reference, re-adding it, then rebuilding the project.
I just created a new empty universal app (windows 10) and checked it in on my visual studio online project.
The configured build is constantly failing on following error...
The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\WindowsXaml\v14.0\8.2\Microsoft.Windows.UI.Xaml.CSharp.targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
I set build configurations to use VS2015 but without any luck.
I keep thinking there's a simple configuration I'm missing here... but can it also be that it's not yet supported?
The project itself is just the standard template from Visual Studio.
I'm having a similar issue running with MSBuild 8.2 target missing under VS2013 Update 5 under Windows 10 TH1. Except my target is Microsoft.Windows.UI.Xaml.Cpp.targets. So not necessarily an issue with Visual Studio but rather the substitution for $(TargetPlatformVersion) in the targets definition:
<Import Project="$(TargetPlatformVersion)\Microsoft.Windows.UI.Xaml.Cpp.targets" />
I'm building a project from Microsoft (https://github.com/Microsoft/winsdkfb), so I don't think this is your problem (meaning you've not done anything incorrect).
I know this isn't an answer, but I suspect we're caught in a gap in the Windows 10 SDK & Tools. Those aren't scheduled to be complete and available until 29 July even though VS2015 has RTM'd. I tried to track down something in the VS2015 release notes without luck.
Just inform the solution I found on this thread.
At the time of writing, it appeared that VSTO serves were not yet updated with
the Windows 10 SDK.
The only way back then to make it run was by creating your own Build VM (through Windows Azure) and link it to your VSTO builds.
I posted the thread and got the answer on the MSDN TFS forum.
I have not tried it right now, but since Windows 10 is officially released now, I guess it may work out of the box.
We now support building Universal Windows Platform (UWP) projects on the hosted build service.
So I have a program I've been making in VB for my company through Visual Studio 2013 Express for Desktop and have not worked on it in a couple of months. When I try to open it, I get the following error:
"The VB project "WindowsApplication1" is targeting ".NETFramework,Version=4.5" which is not installed on this machine."
http://imageshack.com/a/img661/6001/DGAfuk.png
I have all of the .NET frameworks installed including all developer and service packs (even language packs). I uninstalled all .NET frameworks and re-installed each of them without any resolution.
I tried to re-install Visual Studio and even tried changing the Framework (one of the options I have) but I cannot view any code or open designer view if I do so. (http://imageshack.com/a/img633/2109/OJaXbr.png)
The strange thing is this computer is the same one I have been developing this application on for months, so I'm not sure what happened over the last 60 days since I launched it.
Does anyone have any clues as to how I can resolve this issue?
Thanks in advance,
Matt
The path to your project must be Les then 256 Character.
That can be the reason of it.
Make sure the path is short "Copy the project to your c drive "C:\ProjectFolder" and try again".
I have a Windows 7 64-bit computer with Visual Studio 2008 and Visual Studio 2010 Professional installed (C# only).
Now I want FxCop. I read first we should install Microsoft Windows SDK for Windows 7 and .NET Framework 4, so I wanted to do so, but it gives me error and says installation failed, go find more details in some HTML page in a folder path that it does not even exist:
Installation of the “Microsoft Windows SDK for Windows 7″ product has reported the following error: Please refer to Samples\Setup\HTML\ConfigDetails.htm document for further information.
So two questions:
I do not care about the rest of the stuff. I just want FxCop! Do I really need to install this SDK too?
What do you think is the problem when its installation fails?
I had a very similar problem. You don't need to install the SDK to do it. However, you still need to download it which is unfortunate as it is a pretty large download after all. Why it isn't a separate download is beyond me...
Anyway, I extracted the install files I needed by following the information in XXX.
In brief, you need to do this (edited from the link above):
Download the ISO version instead, extract it with 7Zip and locate
Setup\WinSDKNetFxTools\cab1.cab. Open it with Windows and copy out the
file
"WinSDK_FxCopSetup.exe_all_enu_1B2F0812_3E8B_426F_95DE_4655AE4DA6C6".
Rename this to "WinSDK_FxCopSetup.exe" and it should now install.
You can also browse the ISO image with suitable tools rather than unextracting the whole thing.
Given the date of this post, you might have already found the solution, but it may help others who come acros this issue.
From the page above there is a comment linking to another explanation that is better detailed: Liberate FxCop 10.0.