This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Register file extension .xxx for double-click.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 19, 2009
08:20 AM
Register file extension .xxx for double-click.
I'm using basicMSI projects for registering a file extension .xxx. on double-click from windows explore this file with extension .xxx should open with executable .exe file.
In File Types view, I right click on Extensions and add an extension "xxx" (for .xxx). In the properties, I put:
Code:
ProgID: xxxfile
MIME Type:
In the Open Verb properties, I have:
Code:
Command Sequence:
Display Name:
Argument: "%1"
In the ProgIDs folder, there's a new item called xxxfile, for which I entered nothing for these properties:
Code:
COM Class:
Description:
Icon file:
Icon Index:
I have associated key file with .exe in the component.
Now the problem:
----------------
After installation, I see that the files with .xxx extension are associated with the .exe as can be seen in windows explorer(the icon reflects of the one used for exe and the file types). But on double-clicking the file with .xxx kicks off an "installation" kind of screen rather than opening the file in .exe. I can confirm that it is trying to run “self-repair” while trying to open .xxx file.
I confirmed the registry entry on the system and the following is found
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Applications\Viewer.exe]
[HKEY_CLASSES_ROOT\Applications\Viewer.exe\shell]
[HKEY_CLASSES_ROOT\Applications\Viewer.exe\shell\Open]
[HKEY_CLASSES_ROOT\Applications\Viewer.exe\shell\Open\command]
@="\"C:\\Program Files\\\\\\Viewer.exe\" \"%1\""
"command"=hex(7):32,00,5e,00,54,00,35,00,57,00,76,00,30,00,55,00,30,00,3f,00,\
39,00,58,00,57,00,78,00,52,00,5e,00,74,00,48,00,69,00,3d,00,4e,00,65,00,61,\
00,72,00,50,00,6f,00,69,00,6e,00,74,00,53,00,65,00,72,00,76,00,65,00,72,00,\
3e,00,66,00,4d,00,35,00,6d,00,74,00,29,00,53,00,48,00,58,00,39,00,6c,00,2c,\
00,38,00,42,00,4c,00,4d,00,71,00,48,00,24,00,6b,00,20,00,22,00,25,00,31,00,\
22,00,00,00,00,00
-------------
The funny part is if I create standalone demo application using IS2009 with the same viewer.exe and use the above method of registering file type it works. Not sure why there is a problem in integrating the same stuff with my product installer which also installs other binaries.
I thought that it could be a system issue which is not the case since the issue is getting reproduced even in the newer builds.
I am not sure how can I debug this issue but any help in this matter will be greatly appreciated.
Thanks!
In File Types view, I right click on Extensions and add an extension "xxx" (for .xxx). In the properties, I put:
Code:
ProgID: xxxfile
MIME Type:
In the Open Verb properties, I have:
Code:
Command Sequence:
Display Name:
Argument: "%1"
In the ProgIDs folder, there's a new item called xxxfile, for which I entered nothing for these properties:
Code:
COM Class:
Description:
Icon file:
Icon Index:
I have associated key file with .exe in the component.
Now the problem:
----------------
After installation, I see that the files with .xxx extension are associated with the .exe as can be seen in windows explorer(the icon reflects of the one used for exe and the file types). But on double-clicking the file with .xxx kicks off an "installation" kind of screen rather than opening the file in .exe. I can confirm that it is trying to run “self-repair” while trying to open .xxx file.
I confirmed the registry entry on the system and the following is found
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Applications\Viewer.exe]
[HKEY_CLASSES_ROOT\Applications\Viewer.exe\shell]
[HKEY_CLASSES_ROOT\Applications\Viewer.exe\shell\Open]
[HKEY_CLASSES_ROOT\Applications\Viewer.exe\shell\Open\command]
@="\"C:\\Program Files\\
"command"=hex(7):32,00,5e,00,54,00,35,00,57,00,76,00,30,00,55,00,30,00,3f,00,\
39,00,58,00,57,00,78,00,52,00,5e,00,74,00,48,00,69,00,3d,00,4e,00,65,00,61,\
00,72,00,50,00,6f,00,69,00,6e,00,74,00,53,00,65,00,72,00,76,00,65,00,72,00,\
3e,00,66,00,4d,00,35,00,6d,00,74,00,29,00,53,00,48,00,58,00,39,00,6c,00,2c,\
00,38,00,42,00,4c,00,4d,00,71,00,48,00,24,00,6b,00,20,00,22,00,25,00,31,00,\
22,00,00,00,00,00
-------------
The funny part is if I create standalone demo application using IS2009 with the same viewer.exe and use the above method of registering file type it works. Not sure why there is a problem in integrating the same stuff with my product installer which also installs other binaries.
I thought that it could be a system issue which is not the case since the issue is getting reproduced even in the newer builds.
I am not sure how can I debug this issue but any help in this matter will be greatly appreciated.
Thanks!
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 20, 2009
01:53 PM
Does the Windows Event Viewer give you any hint as to what is being repaired/installed when the self-repair is kicked off? Many times you will see an file or component listed as the problem.
(If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 21, 2009
01:19 PM
Thanks SherylSikora for the pointers. After investigating the event log I found the following entries:
1. Detection of product '{ProductCode}', feature '', component '{GUID}' failed. The resource '\' does not exist.
Also the following event viewer entry which actually refers to the component GUID of my .exe application.
2. Detection of product '{ProductCode}', feature '' failed during request for component '{EXE_COMPONENT_GUID}'
So what does these event viewer entries mean to me?
1. From entry 1 above, I confirmed in my installer that I have an empty component that does not have any file in it, so as to avoid any possible upgrade issues.
2. From entry 2 above, is it failing because of entry 1.
Thanks again for your help.
1. Detection of product '{ProductCode}', feature '
Also the following event viewer entry which actually refers to the component GUID of my .exe application.
2. Detection of product '{ProductCode}', feature '
So what does these event viewer entries mean to me?
1. From entry 1 above, I confirmed in my installer that I have an empty component that does not have any file in it, so as to avoid any possible upgrade issues.
2. From entry 2 above, is it failing because of entry 1.
Thanks again for your help.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 23, 2009
06:24 AM
I think I found the solution. The issue was that some folders were removed from the installation. When I manually created these folders the double-click operation started working. I also incorporated the change in my product installer by making entry of missing empty folders in CREATEFOLDER table. This is working fine for me. some useful notes are here as well http://msdn.microsoft.com/en-us/library/aa371546(VS.85).aspx
Thanks again SherylSikora.
Thanks again SherylSikora.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 07, 2013
10:54 PM
Hi,
I am also facing the same problem .Please help us to resolve this.
-Mahender
I am also facing the same problem .Please help us to resolve this.
-Mahender