Magnify 1.22.1 shortcut behavior mystery
Built a package for Magnify, an XBRL document previewer, using Wise Package Studio 8. There's an exe that doesn't reveal any MSI, just some DLLs and a few tmp files. I believe it may be a Java-based install.
Anyhow, I used Wise Setup Capture to create a package, which installs successfully except for one minor issue.
If I install the application from the client's exe, then drag the desktop shortcut to the Quick Launch taskbar (we're running Windows XP Service Pack 3), I can then drag and drop an XML file onto the Quick Launch icon and have the file open in Magnify. That's the desired behavior.
Initially when I did the same with my package, I'd drag the XML file to the icon and nothing would happen.
So I figured I could just copy the shortcut from the original exe and add it to my package. Now I can drag the XML file to the Quick Launch icon and Magnify will start, but the file doesn't open. Tried running Process Monitor to see if anything looked awry and I'm not getting any Access Denied messages, nor does anything jump out as a likely culprit.
Anyhow, I used Wise Setup Capture to create a package, which installs successfully except for one minor issue.
If I install the application from the client's exe, then drag the desktop shortcut to the Quick Launch taskbar (we're running Windows XP Service Pack 3), I can then drag and drop an XML file onto the Quick Launch icon and have the file open in Magnify. That's the desired behavior.
Initially when I did the same with my package, I'd drag the XML file to the icon and nothing would happen.
So I figured I could just copy the shortcut from the original exe and add it to my package. Now I can drag the XML file to the Quick Launch icon and Magnify will start, but the file doesn't open. Tried running Process Monitor to see if anything looked awry and I'm not getting any Access Denied messages, nor does anything jump out as a likely culprit.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Ron, use the vendor's install and follow the trail from HKEY_CLASSES_ROOT\.xml (note the full-stop/period before the 'XML'), to the application ID (probably 'xmlfile' or 'xml.file', down to 'HKEY_CLASSES_ROOT\xmlfile\shell\open\command'. The '(Default)' entry there will show you the command line you need. Recreate that in your MSI and all should be well. I suspect that your current entry is missing the '%1' part.
Posted by:
RonW
13 years ago
I've checked the registry values at HKCR\Magnify.XMLFile, which is "C:\Program Files\Magnify\Magnify.exe" "%1" both in the client install and in my package.
Using Process Explorer, I've dragged files onto the Quick Launch icon for the application, and both my package and the client install fire off the same command:
"C:\Program Files\Magnify\Magnify.exe" [filename]. Process Explorer shows that both of these commands were successful, yet the packaged version only opens the application, not the file.
Using Process Explorer, I've dragged files onto the Quick Launch icon for the application, and both my package and the client install fire off the same command:
"C:\Program Files\Magnify\Magnify.exe" [filename]. Process Explorer shows that both of these commands were successful, yet the packaged version only opens the application, not the file.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.