Missing goal debugging?

Question

When I try to create my solution, I get the following error:

Visual Studio cannot start debugging because there is no debugging target 'c: \ target'. Please> create a project and try again, or set the OutputPath and AssemblyName properties accordingly> to indicate the correct location of the target assembly.

My output path is set correctly to bin \ Debug , but exe is never created in this folder. Instead, all I get is the exe.config , vshost.exe and vshost.exe.config .

Any idea what is going on?

Answer 1

You can open the project file with a text editor and replace "c: \ target" with "bin \ Debug"

EDIT

There are other useful answers, but I can’t delete mine, as it is accepted.

@CZFox Answer

@Yehuda Shapira Answer

Answer 2

• Make sure the project output path is correct (Project> Properties> Build> Output path)
• Go to Build> Configuration Manager and check if your project has main / entry Build. If not, check it out.

Answer 3

I had the same problem:

Here are solutions that didn't work for me:

• Creation / restoration of the entire solution
• Make sure the output path is correct (MyProject> Properties> Build> Output> Output path)

Here's a solution for made :

• Restore only a project

Answer 4

I solved this type of problem by following this step

1.VS2010 right-click on the solution explorer and select Build.

• Press Ctrl + F5 or F5 again

Answer 5

I just stumbled upon this problem, but I am using Visual Web Developer Express 2010 and cannot find any wrong path either in the IDE or in the project file. Restoring or deleting build folders did not help.

But after studying the .user project file, which I had never done before, I found that there was a bad path. Very simple if you know where to look.

Answer 6

You can try the following steps to solve the problem.

Step 1:

Right click on the solution and select the property

Step 2:

In the "Configuration" property, select the "Build" button

Answer 7

I found that this could happen if all files are deleted from the bin folder. ReBuild application for forced full assembly: right-click on the project in the solution explorer and select ReBuild.

Answer 8

To resolve this issue, follow these steps:

• If you work with VS2010, change the target platform of the platform to x64
• Select .net framework as 3.5
• If you use any custom code for Sharepoint and want to debug or deploy using the above ... and my bad sake, I don't use .net applications

Answer 9

I had the same problem and the real solution was awkwardly easy:

If Visual Studio has never compiled a program in your project (before finding the first error), you will get this error. What I did was delete all the code violators (in my case, leaving just the button button1_Click without the code). Run / compile the code once; exit the running program and this message will disappear.

The compiler creates various directories and files in the first successful compiler, and they are used by the debugger. Now I recommend with all new projects, define the form, compile, close, and then start coding.

Answer 10

I also had this error (in VS2010), and in my case (two projects in the same solution with one of them for unit tests) the answer was to go to the solution properties (and not to the project) and set up one project start . I would think that in the project settings in the "Application" section, it is also necessary to indicate "Launch Object", but it works for me with or without it.

Answer 11

Although this has already been answered, I found that my own decision was not one of the above. Admittedly, rookie mistake, as part of my solution, I had several projects, so when I tried to start the solution, the wrong project was installed as Startup Project .

So, in my own case, not to mention the others, the solution was to right-click the project and select Install as launch project

Answer 12

There are many problems that can lead to this problem, after losing two days for this problem, I think I have the main reason for this problem, as well as the problem of the form constructor throwing an error when switching to the Design view (also seems to affect DataSet constructor):

A syntax error of a language that Intellisense does not catch.

As soon as I looked through my code with a thin tooth comb, I found a couple of really unscrupulous errors that I continued to ignore after they were resolved, the solution was just fine, and the output was in the right place.

Answer 13

It was a very unpleasant mistake!

I kept trying to start the debug instance, but it just wouldn't make an exe! Although there were errors in my ConnectionString (when trying to make an SQL connection). There were two backslashes that were supposed to be part of the path, and the textbook I was visiting made me ignore it.

Well, it turns out it was a mistake. The backslash marks the beginning of some escaping you want to do, and the way to display the backslash is \\ instead of \ .

It got rid of, and it worked for me.

EDIT: It would seem that you need to get rid of the tiny mistakes you made by writing your code so that it compiles correctly.

Answer 14

I solved this problem by changing the Target Platform to "any processor."

Answer 15

If the above explanation does not help you, then you may have a program error. I have the same problem, and I solved it, because I cut functions used in one class, and one of the functions was the reason for this.

Answer 16

I had a very similar problem, but almost no solutions worked for me, finally when I reset VS setup, it is fixed ... For reset parameters:

• Service menu>
• Import and Export Options>
• Select reset all radio settings>
• Next>
• Next (you can backup the current settings in this step)>
• Done

Answer 17

Problem: The problem was that I had the wrong nuget source configuration, so the solution could not start properly even though it was built correctly, as it still met the old dll links.

Solution: This was not enough to change the original url source, I just needed to remove the entire nugget source and add it again with the correct url. Clean the solution and restore it.

Answer 18

I tried everything that was mentioned in this thread, but no one worked. Then I tried the simplest thing, and it worked. Close the visual studio and open it again.

Answer 19

Here is the solution to this problem, you do not need to change anything for this problem. You all know that C # is a case-sensitive language, and we must write all the methods and statements in the right case. We all just skipped this thing, and we just need to change the main () method → Main () This thing solved my problem, please let me know if you still find :-)