Diagnostics.Process doesn’t open PDF file using adobe reader

I have the ability to create PDFs in my C#/ WPF application and run them with the following:

Process.Start( _ pathToPDFFile);.

This works with Adobe Acrobat, however not with Adobe Reader. When Adobe Reader is set up, Process.Start() does nothing unless the Reader process is currently running in the Job Manager.
C# pdf processing library: http://www.iditect.com/product/pdf/
How can I get Adobe Reader to reveal the PDF when I try to start a PDF?

Depending also on the variation of Acrobat Reader to release (if different from Adobe Reader 11.0) you might need to alter the course.

The example here just reveals that you must pass the course to acrobat reader explicitly to your Process.Start() by making a ProcessStartInfo object. There is work to do on how this path should be recuperated or constructed. The copying reveals a way by constructing the course, but this can just work if you know the computer systems the app will be carried out on.

Initially, you need to examine if Adobe Reader is the default program for pdf files. You can inspect it in Control Panel -> Programs -> Default Programs -> Set Associations.

If Adobe Reader is the default PDF program, your code needs to deal with Windows 8, actually in most variation of Windows.

If Adobe Reader is not the default PDF program, you need should get course to AcroRd32.exe. This post must help you.

I don’t see your full code, however I solved comparable concern by setting ProcessStartInfo.UseShellExecute to true.

In our case, the problem was only reproducible when beginning the application from Visual Studio – beginning the.exe directly works as anticipated.

After some debugging, it ended up that Visual Studio was set to constantly run as administrator, which triggers the issue. Turning this off (which is hard enough itself) fixes the problem.

I’m having a problem while aiming to open a PDF file using Process.Start(). The program runs the process as a background procedure however no adobe reader window appear. A solution i found was to use chrome.exe, but my customer want to open on adobe-reader, as it’s the default windows program.

Discover a “problem” of Adobe Reader DC. It mantains a level of security that doesn’t let me run it as administrator (don’t ask me why). Check this link to find out more: https://forums.adobe.com/thread/1955530.

Now I’ll search for a solution to run it without administrator privileges, or ask my client to uncheck the checkbox.

So, I have actually found an option for my issue. The Adobe Reader, given that variation 10.0, has a “Protected Mode” setting. I wrote a code to alter that setting in the windows registry, so the user will not have to do that.

You can straight utilize System.Diagnostics.Process.Start(“”) to open with default pdfreader program on respective client system.

Leave a Reply

Your email address will not be published. Required fields are marked *