LAUNCHING Application
-
Hi i need a logic for given issue that i have a interface of third party application in my application (mfc application), using this interface , i launch the third party applicaiton. my problem is that when my appliction exit, the third party applicaiton also is forced to close. Is any alernative this. :) by paul
-
Hi i need a logic for given issue that i have a interface of third party application in my application (mfc application), using this interface , i launch the third party applicaiton. my problem is that when my appliction exit, the third party applicaiton also is forced to close. Is any alernative this. :) by paul
paul crescent wrote:
using this interface
Probably you should read interface documentation (if any). :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[Image resize DLL] -
Hi i need a logic for given issue that i have a interface of third party application in my application (mfc application), using this interface , i launch the third party applicaiton. my problem is that when my appliction exit, the third party applicaiton also is forced to close. Is any alernative this. :) by paul
create a new process of that application
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixturecheers, Alok Gupta VC Forum Q&A :- I/IV Support CRY- Child Relief and You/xml>
-
Hi i need a logic for given issue that i have a interface of third party application in my application (mfc application), using this interface , i launch the third party applicaiton. my problem is that when my appliction exit, the third party applicaiton also is forced to close. Is any alernative this. :) by paul
The devil is in the details for this sort of thing. My main app can sometimes use another company's app to do some work. They provide a COM library to communicate with their app. In a similar way to yours, if my app closes, their COM library closes, and in tidying up shuts down the external app. I'm not complaining - this is a good thing for me. But I can see it being a pain. Do you have some need for controlling this external app? If not, just use CreateProcess / ShellExecute when your app runs, and let the external app do it's own thing. Would your app closing have some bad effect on external app? As I said at the beginning, the devil is in the details. You have to sweat the small stuff. cliché:off. Iain.