F5 or Start Debugging Button is Greyed Out for Winform application?

Question

I know there are many question related to this already on SO but none of them has woked for me till now.

I have a winform application but when I am trying to debug it my Start button is disabled.

Now when I am trying to debug my Start Debugging key is disabled

enter image description here

Things which I have already done are:

1) I have already set my winform application as the Single Start Up project.

2) I have removed the multiple start up project option.

3) I have tried to restart my Visual Studio many times.

4) I have rebuild the application and it is building successfully with no errors.

5) I have build the entire solution and it also build successfuly with no errors.

6) I have checked the sln file and the Format version in it is:

Microsoft Visual Studio Solution File, Format Version 11.00

which I suppose is correct.

Have you tried same solution on some other machine? if that also not working then as u have already tried all other solution looks like you have to share your solution to get us to know what's the problem — Kamran Shahid, Mar 14 '14 at 07:56

score 39 · Answer 1 · answered May 19 '15 at 09:14

39

Go to the solution Explorer Right click on the solution /Project name and choose set as startup project, it should be enabled.

Go to the solution Explorer Right click on the solution /Project name and choose set as startup project

answered May 19 '15 at 09:14

Kamaro

955
1
10
11

1

This is the solution! Thank you! – Luca Steeb Jul 23 '15 at 17:49
1

using visual studio 2019, there is no such "set as startu project" option, so this doesn't work for me – xdavidliu Dec 08 '19 at 16:52

score 20 · Accepted Answer · answered Mar 14 '14 at 08:17

20

I dont know the reason but this one worked for me. I excluded the project from my solution and then build my solution without it.

And then I again added my project and build my solution and set it as Start Up Application and it has worked for me.

(Truly speaking I really dont understand the reasoning for this!)

answered Mar 14 '14 at 08:17

Rahul Tripathi

168,305
31
280
331

1

No, just accept it as an answer and leave it here, so others can benefit of it, when having the same issue. – Max Mar 14 '14 at 10:22
7

I think it is helpful, so I'm going to give you an upvote, it takes 5 downvotes to kill 1 upvote:) – Max Mar 14 '14 at 10:32
2

Keep it here, this particular answer recently helped me with this problem. – SixOThree Jul 21 '14 at 15:20
1

Thank you, you saved me hours ^^ – Luca Steeb Jul 23 '15 at 17:48
Just setting "Set as StartUp Project", without the steps before it, worked right away for me. Thanks for the suggestion! – Josh1billion Jul 08 '16 at 02:35

score 4 · Answer 3 · edited Jun 12 '14 at 05:08

4

Just to add more information to user3414693's post it's possible there is a problem in the solution file such as referencing a project that doesn't exist or has had its name changed.

Unloading and reloading the project will recreate this file with the correct information potentially solving the problem.

edited Jun 12 '14 at 05:08

Andrew Barber

39,603
20
94
123

answered Jun 12 '14 at 01:05

Chiko

81
4

If you have a new question, please ask it by clicking the [Ask Question](http://stackoverflow.com/questions/ask) button. Include a link to this question if it helps provide context. – Jun 12 '14 at 05:32
1

Hi Paulchen, I don't have a new question this post was meant to be provided as an answer to the following posts - https://stackoverflow.com/a/22399535/3732249 and - https://stackoverflow.com/q/22398767/3732249 Can either of you please provide why you feel this is not an answer to the question provided? the problem is potentially a broken solution file and it needs to be corrected, removing and readding will rebuild the file solving that issue i can't directly specify what is broken in the file without seeing it, nor would it be possible as the issue has been resolved, this is for other people. – Chiko Jun 12 '14 at 06:05
I agree with Chiko here, this seems like a perfectly reasonable attempt to solve the OP's problem. The first part suggests a possible cause of the problem and the second suggests an action to take that would resolve it. I can't vouch for the answer's correctness, but it does look like an answer and not a comment or another question to me. – Pops Jun 13 '14 at 03:59

score 3 · Answer 4 · answered Nov 19 '14 at 14:23

3

In my case I excluded the project from my solution and close my Solution. When Open again, The Solution change configuration (F4) to Debug|Mixed Platforms (I don't change manually). Then I changed to Debug|Any CPU and works for me!

answered Nov 19 '14 at 14:23

Hernaldo Gonzalez

1,977
1
21
32

I didn't need to exclude anything. Looking at the solution's Properties window, the Active Config showed "Debug|Mixed Platforms". Changing it as you did and rebuilding fixed the issue. – mono código Jan 11 '19 at 02:06

score 1 · Answer 5 · answered Dec 22 '14 at 15:17

Go to your "Solution Propery Pages" in StartUp Project make sure that if you have "multiple startup projects" selected that you have at least some of those projects available turned on. If there are non active. You will not be allowed to Debug or start your project.

score 1 · Answer 6 · answered Oct 04 '15 at 15:43

1

I have also found that you need to make sure you open up the .sln file in Visual Studio, so that the Solution Explorer displays all the relevant projects. If you open just one of the individual source files, it will not have a context in which to run the program.

answered Oct 04 '15 at 15:43

Spencer Williams

821
10
20

1

I had the same issue in Visual Studio 2017 RC, when opening the solution as a folder. This answer led me to open the .sln file directly in Visual Studio 2017, which solved my problem. Thank you! – arni Nov 29 '16 at 08:29

score 0 · Answer 7 · answered Nov 17 '22 at 15:06

0

I changed to Any CPU and it worked for me.

answered Nov 17 '22 at 15:06

Google Pandit

1

score 0 · Answer 8 · answered Nov 29 '22 at 14:17

0

In case you are in Visual Studio for Mac, going into Unity -> Preferences and clicking on "Regenerate Project Files" fixed it for me.

answered Nov 29 '22 at 14:17

Reinaldo

4,556
3
24
24

score -2 · Answer 9 · answered Apr 30 '19 at 15:35

-2

You need to create a new solution. File -> New -> Solution.

That's all.

answered Apr 30 '19 at 15:35

Wolfpack'08

3,982
11
46
78

Not sure what you mean, but my answer works and is unique, The other answers, as well, suppose that he isn't on a solution. Reproducing this, there's not on a solution. – Wolfpack'08 Jul 11 '19 at 20:32
there is no "solution" in file -> new for me, using VS 2019. – xdavidliu Dec 08 '19 at 16:53
@xdavidliu This was asked 8 years ago for VS 2010 and works in VS Code and some other versions. Thank you for the info. The solution in VS 2019 is different, but I don't have it off-hand: feel free to add it to an edit or a comment if you find it. – Wolfpack'08 Nov 25 '22 at 14:29

F5 or Start Debugging Button is Greyed Out for Winform application?

9 Answers9

Linked