Failed to start debugging. Failed to start launch project. VS2015

Question

I started a new console project in VS2015. I have only this code:

using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; using SautinSoft; namespace PdfParser { class Program { static void Main(string[] args) { string path = Environment.GetFolderPath(Environment.SpecialFolder.Desktop); SautinSoft.PdfFocus f = new PdfFocus(); f.OpenPdf(@"path:\abc.pdf"); if (f.PageCount > 0) f.ToExcel(@"path:\abc.xls"); } } } 

When I try to start, I get the following:

Unable to start debugging. Failed to start launch project. Check the debug settings for the startup project.

How can i fix this? Thank.

Answer 1

After upgrading MSVC2015 to Update3, I had the same problem: instead of std::map , the horrible std::_Tree<std::_Tmap_traits... etc. is displayed in the Watch window, etc. Some plugins started throwing exceptions, some projects failed run in debug mode.

Everything was resolved by removing CurrentSettings.vssettings . It is usually located in Documents\Visual Studio 2015\Settings If not, go to "Tools -> Options -> Environment -> Import and Export Settings" to find the location of this file.

Answer 2

If it were on a completely new ASP.NET Core 1.0 web application.

Solved with restarting Visual Studio.

Answer 3

I'm stuck too. I deleted the bin and obj folders, recreated, and then started.

A very meaningless mistake ....

Answer 4

I had this problem when I tried start (without) Debugging my Asp.Net MVC project

Does Visual Studio run as Administrator

so just restart visual studio As Administrator

Answer 5

In addition to “Cannot start debugging”, I also had errors “Operation could not be completed: Unspecified error” when I tried to rebuild.
Thanks to the Visual Studio pop-up “operation could not be completed” , it was enough to close Visual Studio 2015 and then open it again .

Answer 6

Make sure you start Visual Studio as an administrator.

• Right click on Visual Studio 2015 shortcut
• Select the Shortcut tab
• Click Advanced
• Check the box "Run as administrator" (see below)

This solved the problem for me with the exact error message.

It is not always convenient to run VS in administrator mode. Make sure you uncheck the box after the problem has been fixed.

Answer 7

No need to delete everything in my case, I just opened

"CurrentSettings.vssettings"

submit and commented on this property

 <PropertyValue name="DefaultBehaviorForStartupProjects">1</PropertyValue> 

and everything is fixed.

Sample

Answer 8

I had the same problem and it was resolved by deleting the .vs directory in the project directory.

Answer 9

Just delete the hidden .vs folder. This folder is in the same place as the sln file. Removing this folder also updates the intellisense cache and fixes any problems with it. Hope this helps.

Answer 10

Delete all matching / obj and / bin folders. Run again.

Answer 11

Close Visual Studio and open it again.

Answer 12

Just restart your visual studio and run as administrator.

Answer 13

I had this with the Xamarin.iOS project in my Xamarin.Forms solution. I tried every sentence here, without success.

The source of the error was a misconfigured .csproj project. I never edited it myself and did not even touch on the properties of the project. I am using Visual Studio 2017 RC. I came across a solution when comparing a project file with previous versions in Source Control.

Compare the project file with the previous version and try to dramatically change the changes until you fix the problem and do not know what the reason is.

Answer 14

The solution for me was to delete all *.user files that are usually generated for both solution files and projects

Answer 15

I also found this problem. But after restarting the Visual Studio 2015 community as an administrator, I discovered a new problem:

And then I try to open another solution, close another solution and open the solution with the problem, then solve the problem.

Answer 16

If you have a problem with an existing application, I deleted the vs settings, but the problem remains,

Finally, I just restarted VS and worked fine.

I think that sometimes when we load a project, some library does not load with a solution, so the best option before doing anything is to simply restart VS.

Answer 17

After adding a reference to the MyProjectReference project to my application and then deleting it, I also get the same error:

Unable to start debugging. Failed to start launch project. Check the debug settings for the startup project.

Deleting the configuration, starting as an administrator, rebooting VS, rebooting the machine had no effect.

After starting my web application without debugging (Right-Click Project → View In Browser (Google Chrome), I got a much more useful error:

Failed to load file or assembly "MyProjectReference" or one of the dependencies. An attempt was made to load a program with the wrong format.

My solution was then to re-add back to the solution, and then delete it again. After that, recovery and debugging worked.

Answer 18

As I fixed my problem, I closed the project that had this error, created a new project, built a new project, then opened the project that had the problem and assembled it. It worked for me.

Answer 19

Make sure you close all instances of Visual Studio and then restart with administrator privileges. In my case, I had several instances of Visual Studio open, and I had to close all of them, and then restart Visual Studio with administrator privileges to make it work.

Answer 20

I had Visual Studio 2015 with ASP.net MVC5 developed using DDD (Domain Driven Design). The problem was the same since I just opened Visual Studio normally.

The problem was resolved when I closed all instances of Visual Studio and restarted as administrator.

Answer 21

I also ran into this problem in VS 2015, but finally I solved it by following these steps

In VS go to: Tools → Options → Projects and Solutions → Build and Run

Select "Always build" in "At startup, when the project is out of date"

Answer 22

This problem happened to me with the latest VS2019.
I tried everything here, but, unfortunately, to no avail.

Finally, I restarted the IIS server and manually redesigned the "default application pool".
After debugging, the problem is fixed.

Answer 23

For me, the solution was to run testapp.csproj instead of testapp.sln . This can be selected from the drop-down list next to the green play button.

Answer 24

Just an updated Visual Studio, which then suggested restarting the computer. This is what fixed the problem for me.

Note: I tried some of the above / below, but to no avail.

Answer 25

I solved this problem by clearing the cache of the MEF component.

Use this VS Extension to clear the cache very easily. !!