PDF Help Files

[skj]

I'm working on HP Device Manager Console v4.3 & there are many pdf help files, so do i need to include adobe reader as part of the sequence or it will pickup adobe reader application from the local machine?

[kirk]

Yes and no and maybe:

- If the PDF document is opened from within the virtual application (like via a "help" or "Manuals" Menu shortcut, the call would be passed to the local OS and Adobe Reader would launch. However, the locally running AdobeReader would complain that it cannot access the file (because it is inside the VE)

- Some applications first create a copy of the PDF in a Temp folder (like for a Mail Attachment) and if that temp folder is local, AdobeReader could open it.

- If you have the PDFs as separate shirtcuts (Start Menu) and you don't do anything, probably the first (don't launch) effect will be seen - but if you modify the OSD files to have the local Adobe Reader in the "PROGRAM" field and the path-to-pdf in the "ATTRIBUTE" field, the PDF probably will be opened - because in that case the local Reader is "pulled" into the VirtualEnvironment and as such cann access the PDFs

- You could sequence a PDF reader along with the application so it is also part of the Package. (In this case I wouldn't use Adobe Reader but Foxit or Nitro PDF Viewer, because they are more lightweight)

- You could have an AdobeReader App-V Package and use Dynamic Suite Composition to link it to the main app

[Simbad]

Yes and no and maybe:
- You could sequence a PDF reader along with the application so it is also part of the Package. (In this case I wouldn't use Adobe Reader but Foxit or Nitro PDF Viewer, because they are more lightweight)

This doesnt work for me, actually the File Type Association of the local machine will override the virtual PDF sequenced in the package.

But I've found a solution that consist of scripting the launch of a .reg file in the VE that will overwrite the HKEY_CLASS_ROOT entries regarding PDF association to map the virtual PDF reader. And for now it works... but never understood why the sequenced FTA are not working by default. I have 3 packages like this (using virtual middlewares in the same bubble : 2 with PDF and 1 with Word Viewer). Local FTA will always override the virtual FTA if I dont run a registry file to rewrite HKEY_CLASS_ROOT.

[balthazar]

PDF help files are pretty annoying, the only other solution I've seen was to set their shortcuts to "C:\Program Files (x86)\Adobe" etc' on down to the acrobat executable.

Of course, hardcoding paths makes me cringe, but...it's marginally better than including acrobat and runtime overwriting FTA's.

If your acrobat reader is virtual btw you CAN suite the two and as long as the package is setup right, it will be able to see the help files. Well, should, if it feels like it, and it's tuesday.