[SOLVED!] How to fix Unverified Breakpoints

DanM · August 13, 2019, 10:12am

I wouldn’t think it’s anything wrong with Code
Are you absolutely sure you are opening Visual Studio Code from the developer command prompt?

Also the build task doesn’t create a build folder if it doesn’t already exist so you need to manually add it yourself, otherwise the task won’t work.

enricodegan · August 13, 2019, 2:40pm

Hi @DanM,

I’m tried an ultimatum solution by uninstalling and reinstalling VS Code. But … you were right, it didn’t solve any problems and actually added a new one. Now my #inclde's aren’t working in all of my files.

Do you know how I could fix this? I’m on the newest version of Visual Studio Code by the way.

Also, where can find the developer command prompt? It is just the integrated terminal?

Thanks,
Enrico

DanM · August 13, 2019, 3:52pm

I think there’s been some miscommunication.

Launching Code from the developer command prompt. Not compiling.
Open the start menu, search for Developer Command Prompt then type “code” and hit enter.
VS Code should launch and cl should now work in the integrated terminal.

enricodegan · August 13, 2019, 4:21pm

Hi @DanM,

Pardon my complete ignorance, but nothing shows up when I type “developer command prompt.”

Would you mind providing me with some screenshots?

Sorry about the miscommunication by the way.
Thanks,
Enrico

DanM · August 13, 2019, 5:10pm

And nothing came up for “Developer”?

enricodegan · August 13, 2019, 6:32pm

Hi @DanM,

No, nothing comes up when typing just “Developer.”

I tried looking this problem up and I found a similar problem on StackOverflow and this was the solution:

VSCode is much more light-weight and is, in essence, a completely different product. VSCode doesn’t ship with a complete setup of MsBuild and of the compiler frameworks that ship with the full version of Visual Studio. You can install these alongside VSCode if You need them by installing “Build Tools for Visual Studio 2017”, you can find the installer all the way at the bottom of the Visual Studio download page.
Therefore, when you type "Developer … " something shows up probably because you have Visual Studio installed.

Do you think I should try and install Build Tools for Visual Studio 2019?

As always thanks for your input,
Enrico

StackOverflow post:

DanM · August 13, 2019, 7:03pm

Now I’m slightly confused. Did you uninstall Visual Studio? How were you able to compile beforehand?
If you had access to cl before you should have the developer command prompt.

Though yes, install the C++ build tools or VS Community with the C++ workload.

enricodegan · August 13, 2019, 7:31pm

Hi @DanM,

I downloaded the Build Tools for VS and now have access to the Developer Command Prompt. I tried what you said in Post #30, but cl still didn’t work.
I’m also very confused because before I was able to compile with absolutely no problem.

Also, I’m still having a problem with the #include that I talked about in Post #29.

What do you recommend that I do?

Thanks,
Enrico

enricodegan · August 13, 2019, 7:45pm

Hi @DanM,

I found this website:

It has information on how to configure the compiler. I think this is the key to breaking the safe but I’m having a bit of trouble finding what I need. On step 3 of the website it says:

Find the Compiler path setting. VS Code will attempt to populate it with a default compiler based on what it finds on your system. It first looks for the MSVC compiler, then for g++ on Windows Subsystem for Linux (WSL), then for g++ on Mingw-w64. For MSVC, the path should look something like this, depending on which specific version you have installed: “C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe”.

I can’t find anything under that path of my computer. Even when I search for cl.exe across my entire computer, file explorer still says that it can’t find it?
I have no idea how my cl.exe file was deleted, but do you know how I can get it back or find a new one?

Thank you so much,
Enrico

P.S. I’m still having a problem with the #include that I talked about in Post #29. I’m not sure if it will go away when this other problem is solved…

DanM · August 13, 2019, 7:47pm

Just to be clear, what exactly did you do? Please provide the steps you took, just so we don’t get a repeat of miscommunication with assumptions.

Does typing cl in the developer command prompt give expected output?

For the include check the course on Udemy. I wrote an article lecture before the "Hello, World!’ one.

Edit: what you linked is for Intellisense and will fix your include issue. It has nothing to do with compiling.

enricodegan · August 13, 2019, 7:48pm

Hi @DanM,

This is what happens when I type cl in the Developer Command Prompt:

I’ll check out the article on Udemy.

Thanks!

DanM · August 13, 2019, 7:52pm

Could you show what you have installed?

Start menu > Visual Studio Installer > Modify

enricodegan · August 13, 2019, 8:36pm

Hi @DanM,

I didn’t download anything extra, just the MSBuild tools.

Thanks,
Enrico

DanM · August 13, 2019, 8:42pm

You didn’t install it. You need to tick the box for C++ Build Tools.

enricodegan · August 13, 2019, 8:45pm

Hi @DanM,

Should I tick/untick any boxes? Or would you say the optional 4 plus the build tools are good enough?

Thanks,
Enrico

DanM · August 13, 2019, 8:50pm

That should be enough

enricodegan · August 13, 2019, 9:05pm

Hi @DanM,

Thank you so much! I can finally compile again!
I have no idea how this error came about because I never remember deleting anything. Anyways, the important thing is that I can now compile and continue with the lectures.

You probably wish this was over … but I still have two more questions: (sorry …)

Where can I find the article on #include in Udemy. What section is it under and what name is displayed in Udemy?
My terminal continues to say this:

What does this mean? Is it something I have to fix that will hurt me down the line or is it fine?

Again, thank you so so much for helping me through this!

Thanks,
Enrico

DanM · August 13, 2019, 9:08pm

It’s under the TripleX section, I believe I called it “A note to Windows Users”
That’s the output. The output of the compilation was those files.

enricodegan · August 13, 2019, 9:33pm

Hi @DanM,

Thank you! Everything is working now!
Debugging is still a problem, but I’ll wait to affront that issue again in the next project.

Thanks again for helping me because I certainly couldn’t have done it without you!

Thank you,
Enrico

enricodegan · August 13, 2019, 9:51pm

Hi @DanM,

Actually I was too curious to see what would happen when I debug…
So I went back to the original project (which is now working by the way!) and pressed F5. Debugging seems to be working correctly after I changed to "externalConsole": to true.
What doesn’t seem to work is building. When I press “Ctrl+Shift+B” I get this in the console:

Is this occurring because I changed "externalConsole": to true? How can I fix it (that way I can return to my original project…)?

Thanks!
Enrico