Similar Posts

Subscribe
Notify of
12 Answers
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
regex9
1 year ago

See if your project can be built at all.

  1. Start Build: Build > Build
  2. Open output window: View > Output
  3. On the one hand, the output window should see whether the build was successful (succeeded/failed/up-to-date/skipped) and if so where the exe file was created.

If you fail, you will find error information either in the output window or in the error list (View > Error List). An exe file is typically not created.

Once the build was successful, you can use the debugger via Debug > Start Debugging start.

verreisterNutzer
1 year ago
Reply to  regex9

Thank you

verreisterNutzer
1 year ago
Reply to  regex9

The build was successful yet I can’t debugging

regex9
1 year ago

And where was the .exe file stored?

verreisterNutzer
1 year ago

Build started at 13:26…

====== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==================

======= Build completed at 13:26 and took 00,031 seconds ===============

regex9
1 year ago

Look into the build log from the output window. If it does not stand there, perform a rebuild (Build > Rebuild Solution) and look again into the issue.

verreisterNutzer
1 year ago

I don’t think so or so

tunik123
1 year ago

Newer versions of the Visual Studio can be configured in such a way that the Debugger is looking for the EXE elsewhere than where the linker has placed it. I never had this problem with old versions. Here are two Scrennshots of settings as I use them:

verreisterNutzer
1 year ago
Reply to  tunik123

Is that the new version?

tunik123
1 year ago

This is MSVC 2019 professional.

tunik123
1 year ago

The problem occurred to me when I ported old projeks to the new version. I used to put the EXEn elsewhere (so that my colleagues can try it out) and the debugger also found it there. Recently there were problems.

verreisterNutzer
1 year ago

achso because I don’t find it