msbuild this application couldn't be started - windows-8

i've got computer with Windows 8 and fresh installation of Visual Studio 13 Express.
I'm working on project which runs on .NET 4.0 Client profile.
Problem is when i try to complile, this error message is shown:
Solutions:
social.msdn : This one says:
try to restart your VS and rebuild - not working
check MSbuild from promt - not working (Message is shown twice)
I also checked project configuration vsproj and tried to make sample project
Reinstall framework:
i tried ot reinstall almost everything, framework, sdk.
when i've installed .NET Framerork v4.5.2 my VS was unnable to start and anoter .NET apps complied before had missing library
I haven't tried to reinstall VS, yet. (But i dont think if it helps)
Edit: Temporary solution shoud be Visual Studio Express 2012, but it not solves problem.
Reinstalaion of VS didn't help.

Related

Web Setup Project on Visual Studio 2022 - Unable to open project error

Good evening,
I have created a Web Form using Visual Studio 2022, and I have created a Web Setup project to help our customers to install the site on their server. I used the official extension that allows to create Setup projects in VS2022 (Microsoft Visual Studio Installer Projects); everything worked fine until some days ago, when VS2022 started to show the following error when trying to load the installer project:
"Unable to open project .../Setup.vdproj".
This is the error I am getting when I try to open/create a Web Setup project
I tried to open it also with VS2019, which I still had installed on my computer, but I got the same error.
At the beginning I thought it was an issue related to the project (maybe for some reasons some files had been corrrupted), so I tried to create a new Web Setup project, both on VS2022 and VS2019. Again, the same error appeared, on both versions of VS. At this point I tried to load the already existing project on another computer, and on the other computer everything worked perfectly, the project was loaded immediatly and no issues have been detected.
I tried to unistall and re-install the Microsoft Visual Studio Installer Projects extension, it didn't solve the problem; I tried to repair VS2022, it didn't solve the problem; I tried to completely uninstall VS2022 and VS2019 and re-install only VS2022, and guess what? It didn't solve the problem.
Does anyone know how to fix this problem, and what is the reason why I am unable to neither load nor create Web Setup projects?
Thank you,
Giacomo

Unable to start program "C:\Program Files\dotnet\dotnet.exe"

I've installed .NET Core 1.0.1 to use with VS 2015 Update 3 and I'm running as Administrator (on Windows 8.1 x64).
If I create any .NET Core project, be it console or web and attempt to run it Visual Studio then comes up with an error:
However I'm unable to ascertain why. VS builds it fine and I can run it from the CLI. I can also run Core fine through VSCode.
I've tried:
Deleting project.lock.json
Deleting the .vs folder
Repairing the .NET Core install
Repairing the VS 2015 install
Uninstalling and reinstalling .NET Core/SDK/Tooling & VS
Rebooting
And it still refuses to work!
I've raised this on the Core Tooling GitHub as well as can be seen here but as yet we're all a little stumped.
There are some people who have problems with Internet Explorer and Visual Studio.
Attempt to install Internet Explorer 9, or set a different default browser.
Other approaches:
Was the data path checked?
Perhaps there are wrong configured environment variables?
Are you sure that the configuration was reset by the installation?
Perhaps the path for the temporary data has been changed?
Try re-installing needed redistributables, as they are needed for executing .Net Core on Windows, as it is stated here :
https://learn.microsoft.com/en-us/dotnet/articles/core/windows-prerequisites
"NET Core requires the VC++ Redistributable when running on Windows"
If it don't work, add a try/catch at the highest level of your application and log all System.Exceptions that may occur. It may give you more informations about this error.
This error occurs if you change the name of the project. To work around this error You will have to delete all files under \object and \bin folders. After that rebuild application.
Restart the visual studio in administrator mode. This solved my problem.

VS2015: The components for communicating with FTP servers are not installed

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!

Visual Studio online build failure for an empty universal app

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.

Testacular install fails, no vcbuild.exe

I'm trying to install Testacular (using nmp) on a Windows 8 Professional (64 bit) laptop, but it fails when it tries to install socket.io as part of this process. The error I get is
Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual
Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere.
I apparently have .NET framework 3.5 installed (it's checked under the add/remove Windows components bit in Control Panel), although I've not managed to find a vcbuild.exe. I tried installing an old copy of VS2005 but this resulted in a different error about an invalid project (.vcproj) file.
Can anyone suggest how I might get this working? Weirdly it installed fine on my work computer, which is very similar to the one on which it won't install (they're both 64 bit Win 8 Pro).
I ran into the same issue. I fixed this by adding this to environmental variable PATH: C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcpackages so that it can find vc build.
In Visual Studio 2010, the command line tool vcbuild.exe is replaced by msbuild.exe. So, please make sure you have right Visual studio.