CDialog assertion failed on VS2005 (it woked fine on VC6)

Question

0.00/5 (No votes)

See more:

Hello,

I have used CDialog class in VC++ Visual Studio 6.0 which worked fine but now when I use the same in Visual Studio 2005 I m facing the problem of Debug Assertion failure

Wht must be the reason?

Thanks
Pritha

Posted 23-Sep-10 2:53am

prithaa

Updated 23-Sep-10 3:15am

CPallini

v2

Add a Solution

4 solutions

Solution 4

Ensure all IDC_* constants are valid. There might be one or more constants (defined in resource.h) but not in actual dialog resource.

Posted 27-Sep-10 8:50am

Ajay Vijayvargiya

Solution 1

You cause an assertion when you do something MFC's programmers thought was a big dodgy. Have a look at where the assertion is fired and see if you can work back to your code and see what caused it.

Cheers,

Ash

Posted 23-Sep-10 3:08am

Aescleal

Updated 24-Sep-10 8:29am

v2

Solution 2

Please provide some more details, where exactly are u getting the debug assertion failure. (provide code snippet if poss)

Posted 23-Sep-10 18:05pm

ganeshkawade2003

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Cedric Moonen · Accepted Answer · 2010-09-23T20:22:00

Solution 3

The best way to fix a problem like that is to first use your debugger to see where things went wrong and for what reason. Then, if you are stuck, come back here and post all the information you gathered with the debugger.
There's no way somebody is going to find what the problem is with so little information.

Posted 23-Sep-10 20:22pm

Cedric Moonen

Comments

prithaa 24-Sep-10 2:30am

Reason for my vote of 5
Automatic vote of 5 for accepting answer.

ThatsAlok 24-Sep-10 2:46am

Best solution I think :-)