1. I use the wizard or the icons to associate an extension (e.g. .ext) with my application but it only works sometimes. Most of the time, double-clicking on a file with .ext launches an attempt to run the installer and then leads to a failure as the .msi file is missing (I have been using .exe install files).
Typical behaviour under Vista is like this:
a) Prior to install: .ext not associated with an app
b) After install before app is run: double-clicking on .ext file runs app (as desired)
c) After app runs and is closed: double-clicking on .ext file launches an installation attempt by Windows as described above. Windows goes looking for an .msi file at C:\Users\myname\AppData\Roaming\myco\myapp\install\
In the Registry, there is a GUID under Installer/Products with SourceList that points to this location. It gives the ProductIcon as
C:\Windows\Installer\{GUID}\ext_1.exe (there is no such folder). In AI I assign the icon from the App.
Under HKCR\Myco.Myapp.ext\shell\&Open\command there is the key/value 'command' qWw0.o,I(=L.3a^Kv}MEMainFeature>dRY9O'8[]A!Yiwt0nl%U "%1"
deleting this eliminates the problem. I don't want to hard code this into my app. How can I prevent this situation arising? It seems your other clients are not complaining about this so how do I have this problem? There does not seem to be any items in the AI project that relate to this. HELP.
2. I tried to create an .msi file with AI to allow inspection of the fields. I tried running the resulting .msi file on a Vista box to do an install but Windows rejected this saying it was not a valid install file and 'contact the vendor'. It works on XP. Why is this? The .exe files run the install just fine apart from the extension registration.
FOLLOW US
Get the latest news in Application Packaging