Menu
I'm working with some C++, and I had a typo in my code causing this. In the future I'd rather Visual Studio would break directly on the faulty code when running in DEBUG MODE directly from Visual Studio 2017 (Community Edition), with the actual expression, rather than showing me this annoying prompt.
Is there a setting for this somewhere?
778
An assertion statement specifies a condition that you expect to hold true at some particular point in your program. If that condition does not hold true, the assertion fails, execution of your program is interrupted, and this dialog box appears. Click. To. Retry.
You may uninstall Microsoft Visual C++ Runtime Package from Program & Features then reinstall it again. Thereafter, check if the issue persists. You may run system file checker [SFC] scan on the computer which will replace the missing or corrupt files & check if the issue persists.
Tell the debugger to break when an exception is thrown In the Exception Settings window (Debug > Windows > Exception Settings), expand the node for a category of exceptions, such as Common Language Runtime Exceptions. Then select the check box for a specific exception within that category, such as System.
In Visual Studio, go to Debug / Windows / Exception Settings. In the Exception Settings, go to Win32 Exceptions / 0xc0000420 Assertion Failed. Uncheck the box in front of that entry.
Is there a setting for this somewhere?
You could do it programmaticaly by setting report mode:
_CrtSetReportMode(_CRT_ASSERT, _CRTDBG_MODE_DEBUG);
The required header is <crtdbg.h>.
114
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
