Re: Hello,I solved the problem!-jc
I dont know the solution really, but quickly tested one old code which does
not have this problem what you describe. It might have other problems though
:). It launches new instance of the parent application. If you close one of
the exe s then the other one still remains.
char modFileName[MAX_PATH];
// get path including name of executeable
GetModuleFileName(NULL, modFileName, MAX_PATH-1);
PostMessage(WM_CLOSE);
// sanoma voidaan l?hett??
bool bSucceed;
STARTUPINFO suInfo;
PROCESS_INFORMATION pi;
memset(&suInfo, 0, sizeof(suInfo));
suInfo.cb = sizeof(suInfo);
CString strExeFileName(modFileName);
bSucceed = CreateProcess(
NULL,
modFileName, //strText.GetBuffer(0),
NULL,
NULL,
FALSE,
NORMAL_PRIORITY_CLASS,
NULL,
NULL,
&suInfo,
&pi
);
// strText.ReleaseBuffer();
if(!bSucceed)
{
// ohjelman k?ynnistys ei onnistunut
CString strMsg;
strMsg.Format("Could not execute:\n%s", strExeFileName);
AfxMessageBox(strMsg);
}
Eric Lemanissier wrote:
Hello,
I have the exact same problem, could you please tell me how you
solved the problem?
Thanks,
Eric
On Wednesday, April 21, 2010 12:34 AM jc wrote:
Hello,
I am using CreateProcess(...), and it is working OK.
However, once the main program closes, the "launched" program
also closes.
How can I have the "launched" program stay open, after
the main program closes?
VC++ 2008, WinXP
TIA,
-jc
On Wednesday, April 21, 2010 3:08 AM jc wrote:
Hello,
I solved the problem!
-jc
Submitted via EggHeadCafe
.NET Windows Services - Timer, Debugging, and Installation
http://www.eggheadcafe.com/tutorials/aspnet/0ddb1434-d3c9-424c-8b12-bdf75c50588c/net-windows-services--timer-debugging-and-installation.aspx