Mark,
Personally, I would do neither. I would create an install package which
includes the install for the Adobe Acrobat reader so that you can make the
assumption that it is installed.
If you can't do this for some reason or another, and you are embedding
the reader in your app as an ActiveX control, then you could try and create
an instance of the control, and if it fails, you know it's not installed
(you will have to have an interop assembly as a reference in your app for
this).
If you are using the reader externally, then I would go with checking to
see if the extension is mapped to anything. However, I would consider this
solution to be very brittle, and my last resort. After all, a different app
could be registered to handle the PDF extension.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard. caspershouse.co m
"Mark Rae" <ma**@markNOSPA Mrae.netwrote in message
news:%2******** ********@TK2MSF TNGP02.phx.gbl. ..
Hi,
I've been asked to write a WinForms app which will create reports as PDF
documents.
The client has agreed that all desktops (WinXP Pro, 32-bit Vista Business)
*will* have Adobe Acrobat Reader installed but, in the interests of
robustness, I want to check for this when the app loads.
Would you recommend checking for the Adobe Acrobat Reader specifically, or
just checking that the .pdf file extension has a valid association?
Any assistance gratefully received.
Mark
--
http://www.markrae.net