Visual C++ 2010 application crash ProcessShellCommand() when is launched in XP

Question

0.00/5 (No votes)

See more:

Hello people, I need help, please, I just did and application MFC SDI in visual studio 2010 C++ ultimate, in windows 7, the program is for win32 x 86 targets, and I did the install file msi as an install project.

When I install it in Windows 7 computers everything is fine, the problem is when I install it in windows XP or Vista. at the beginning everything seem work all right, I can install it, and I can open it, but at the moment of showing the window it crashes and says "Unhandled exception MFC100UD.DLL access violation". I have been trying to find the bug and find out that it happens in the function CWinApp::ProcessShellCommand is called in the CWinApp::InitInstance(), is there any solution for this issue.?

Many thanks.

Mauricio Ruiz

Posted 3-Apr-12 23:32pm

mauruizl

Updated 3-Apr-12 23:53pm

v2

Add a Solution

Comments

Mohibur Rashid 4-Apr-12 5:41am

Very little information. but i would suggest you to debug it on xp mode

Jochen Arndt 4-Apr-12 6:23am

As already noted, you should try to debug to give more information. ProcessShellCommand() opens the document file passed on the command line or creates a new empty document. So the violation may occur anywhere in the document, child frame or view initialization.

1 solution

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)

Marius Bancila · Accepted Answer · 2012-04-06T02:13:00

Do you distribute the VC++ library DLLs (MFC, CRT) in your app folder or do you rely on the redistributable packages? (Microsoft Visual C++ 2010 Redistributable Package (x86)[^] or Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)[^] if you have the SP1 installed. Notice there are other packages for x64 and IA64)

Use depends.exe (www.dependencywalker.com) to make sure all the dependencies of your app are available on the target WinXP machine.

Also, make a habit of distributing Release builds and not Debug builds. I can see you are distributed a Debug because it depends on MFC100UD.dll. A release build would depend on MFC100U.dll.