C#, App.Exit() is not closing Acrobat process.

[Metal_Detector@adobeforums.com]

In my C# Application, I am using Acrobat to merge PDFs.

private static CAcroApp mApp;

//Initialize Acrobat by creating App object
mApp = new AcroAppClass();

//Hide Acrobat
mApp.Hide();

//MERGE PDFs Here//

//Close Acrobat
mApp.CloseAllDocs();
mApp.Exit();

When I open up Task Manager, I can see Acrobat is still running and has the merged pdf open. Is this a known problem?

[Leonard_Rosenthol@adobeforums.com]

I don't recall a "closeAllDocs" method...I would be sure to close down each document individually.

Also, depending on what version of Acrobat you are using, it may/will stay up as long as about 30-60 seconds after you ask it to close...

[Metal_Detector@adobeforums.com]

I am using Acrobat 9 Pro and it doesn't close the process no matter how long I wait after calling mApp.Exit()... Any other ideas to why it isn't closing?

[Leonard_Rosenthol@adobeforums.com]

Check that all documents closed properly...

[Metal_Detector@adobeforums.com]

Thanks for your suggestions!

The problem is, I am using PD Layer to merge all the documents... I can remove all the mApp calls and it will still merge.. And I do close all the documents properly with no exceptions. With or without the mApp calls, the Acrobat process still exists in task manager.

Is there a way to close the Acrobat process through the PD Layer?

[Leonard_Rosenthol@adobeforums.com]

Nope. Only the app.Exit().

of course, you can always use standard Windows API calls...

[AxelArnoldBangert]

Hi,
in my application the acroApp process is "somehow" bound to the calling process. So when I trigger the acroApp.exit() from my calling process nothing happens. But when I close after that the calling process this effects, that the acroApp process is shut down automatically after 16 seconds.

I guess, that we have to open the acroApp process in a new thread. After that it will be independant and we can shut it down since running forth the calling process.
Best regrads
Axel Arnold Bangert - Herzogenrath 2011

[Unregistered]

Hi,
in my application the acroApp process is "somehow" bound to the calling process. So when I trigger the acroApp.exit() from my calling process nothing happens. But when I close after that the calling process this effects, that the acroApp process is shut down automatically after 16 seconds.

I guess, that we have to open the acroApp process in a new thread. After that it will be independant and we can shut it down since running forth the calling process.
Best regrads
Axel Arnold Bangert - Herzogenrath 2011