vc++ createprocess doesn's work after I set up from setup package but work in release folder

Question

1.00/5 (1 vote)

See more:

Hello, all,

I wrote an app by c++ 6.0
but the function createprocess doesn's work after I set up from setup package but work in release folder.

Does anybody has any idea?

Thanks in advance!

rosone

Posted 15-May-11 19:51pm

rosone

Add a Solution

Comments

ShilpiP 16-May-11 1:57am

Share code and try to elaborate your problem.

Sandeep Mewara 16-May-11 2:48am

Elaborate more.

2 solutions

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)

Joan M · Answer 1 · 2011-05-15T20:31:00

Solution 1

Without seeing a bit of code and trying to understand your problem...

Could it be that you have a hardcoded path?

Try to add more information in your question and paste some code...

Posted 15-May-11 20:31pm

Joan M

CPallini · Answer 2 · 2011-05-15T22:30:00

There may be several of reasons why your application's CreateProcess fails. For instance, as Joan Murt correctly pointed out, you may have a hardcoded (relative) path assuming the Release folder as current directory. Anyway, when Windows API functions fail, you can usually collect useful info calling GetLastError.