Description files.
I have just packaged an application that needs a testfile to carry out the testing of the app. This testfile is a description file which when you double click on pops up a dialog box to prove that the app works.
The initial test of my MSI shows that it works ok but the second test which is to click the desc file, nothing happens. The desc file was tested on a machine that had the app manually installed and it worked ok but wouldn't work when the app is installed with my MSI.
The desc file runs on a batch file which was set in the registry during configuration which was captured in my snapshot, and these is all the desc file needs to work.
Any help/ideas would be appreciated as am at a crossroad right now.
The initial test of my MSI shows that it works ok but the second test which is to click the desc file, nothing happens. The desc file was tested on a machine that had the app manually installed and it worked ok but wouldn't work when the app is installed with my MSI.
The desc file runs on a batch file which was set in the registry during configuration which was captured in my snapshot, and these is all the desc file needs to work.
Any help/ideas would be appreciated as am at a crossroad right now.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
kkaminsk
18 years ago
Not sure excactly what you are doing. Are you are using a file association to open the test file or are you launching a batch file that opens the test file?
Posted by:
teejay2
18 years ago
This test file has got like a icon which you can double click on and launches a dialog box. If that makes any sense. The batch file in question is already in program files. So once the icon which has a .desc extension is double clicked on it should launch. But its not doing it.
Cheers.
Cheers.
Posted by:
kkaminsk
18 years ago
Well it sounds like an odd way to get things done. I would make a regular icon that Windows Installer can support that launches the batch file but before that you should check if the app is properly installed. I am assuming that you are performing a regular installation opposed to an advertised installation. If you are using an advertised installation you should double check that all the needed components are in fact installed. I would double check if the batch file works at this point because that should give you a clue as to if the MSI is fully installed. If the batch file works then it has to be something to do with the icon. At that point I would make a proper Windows Installer shortcut opposed to using a file type to trigger the launch of the icon.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.