[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 507
  • Last Modified:

MFC debug assertion message

Hi,

I have developed a console app with
MFC support in Visual Studio 6.
The problem is when I run it in
another PC that has visual studio 6
installed, I get the a message
"Debug Assertion failed" right away.
When I re-compile it on that PC,
the program runs fine.

What is the problem here ? Should I be
doing a setup program and using
that to install it on other PCs ?

Thanks.

0
kkandasa
Asked:
kkandasa
1 Solution
 
mjswartCommented:
I think you should determine the cause of the Debug Assertion and address that issue. Sorry, I can't be any more help, but finding out all you can about the problem is wise advice.

A setup program is only a fancy way of copying files over so I wouldn't put too much hope into that solution.

Knowledge is power,
cheers,
M
0
 
kkandasaAuthor Commented:
How can I find this out ?
0
 
MaroyCommented:
I would ensure that both computer have the same (visual studio) service packs installed.

At our lab we often leave "completed" utilites on systems that have been compiled in the debug mode.  

It is not uncommon for us to have recompile these programs because they "mysteriously" stop working after a service pack or Y2K patch.  One would think that you would get a DLL version error or some such thing, but this does not seem to be the case.

I would assume you would see the same thing if you moved a "working" program from one machine to another and you started getting strange asserts, especially if recompiling on the local machine cures the problem.
0
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

 
kkandasaAuthor Commented:
Hi,

Is there a way to do a setup/install
program for this ?. The package & deployment wizard in Visual Studio tools
is only for visual basic projects.
0
 
kkandasaAuthor Commented:
I get the following error when
compiling the app on another PC with
Visul Studio C++. Even though they
are two PCs, the compiler is supposed
to be the same. I have to choose
rebuild all to get it to work.

Where can I look to
ensure the service packs are the same?

================
fatal error C1853: 'Debug/pCommMan.pch' is not a precompiled header file created with this compiler
===============

Thanks.
0
 
dsandfordCommented:
Are you running a Debug build of your program?  A Release build could make this disappear.
0
 
kkandasaAuthor Commented:
This is true. A release build does
fix this.

How would I do a setup for this ?
0
 
dsandfordCommented:
Not sure what you mean - A setup.exe using InstallShield?  A free evaluation version on InstallShield comes with VC++6 I think, and it is possible that you could download it from Microsoft.

Watch out though - this doesn't answer why the assert occurs in the first place - it is better to determine the root cause.

Under NT - I think the NT service pack can be found by looking at the message at the top of the blue screen at reboot - although it has been a while since I needed to look!

VC service pack installation used to leave a installation log in the root of the C drive.  Check there.  If you are not sure if it is installed, I would advise re-applying it anyway.
0
 
kkandasaAuthor Commented:
Thanks. Please reply so I can award you the points
0
 
dsandfordCommented:
Are you running a Debug build of your program?  A Release build could make this disappear.

Not sure what you mean - A setup.exe using InstallShield?  A free evaluation version on InstallShield comes with VC++6 I think, and it is possible that you could download it from Microsoft.

Watch out though - this doesn't answer why the assert occurs in the first place - it is better to determine the root cause.

Under NT - I think the NT service pack can be found by looking at the message at the top of the blue screen at reboot - although it has been a while since I needed to look!

VC service pack installation used to leave a installation log in the root of the C drive.  Check there.  If you are not sure if it is installed, I would advise re-applying it anyway.

Daz

0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now