installing context mneu handler

[codymanix]

How can I add an entry to the system context menu (when I right-click on a
file). I want a new entry in that context menu that runs my application,
such as packers or virusscanners do it.

 

[David Lowndes]

How can I add an entry to the system context menu (when I right-click on a

file).

Depending on the complexity of what you want to achieve you can just
add registry entries to the HKEY_CLASSES_ROOT\*\shell\open\command, or
create a context menu shell extension. If you just want to run your
application with the file name as a command line parameter, simple
registry entry additions will be enough.

Dave

 

[David Lowndes]

How can I add an entry to the system context menu (when I right-click on a

file).

Depending on the complexity of what you want to achieve you can just
add registry entries to the HKEY_CLASSES_ROOT\*\shell\open\command, or
create a context menu shell extension. If you just want to run your
application with the file name as a command line parameter, simple
registry entry additions will be enough.

Dave

 

[codymanix]

How can I add an entry to the system context menu (when I right-click on
a

Depending on the complexity of what you want to achieve you can just
add registry entries to the HKEY_CLASSES_ROOT\*\shell\open\command, or
create a context menu shell extension. If you just want to run your
application with the file name as a command line parameter, simple
registry entry additions will be enough.

Thank you, David. The thing with the registry worked but now unassigned
filetypes (the ones that haven't a default open command defined) are now
opened by my app by default which was not my intention :-(
Is there a workaround to that?

 

[codymanix]

How can I add an entry to the system context menu (when I right-click on
a

Depending on the complexity of what you want to achieve you can just
add registry entries to the HKEY_CLASSES_ROOT\*\shell\open\command, or
create a context menu shell extension. If you just want to run your
application with the file name as a command line parameter, simple
registry entry additions will be enough.

Thank you, David. The thing with the registry worked but now unassigned
filetypes (the ones that haven't a default open command defined) are now
opened by my app by default which was not my intention :-(
Is there a workaround to that?

 

[David Lowndes]

Thank you, David. The thing with the registry worked but now unassigned

filetypes (the ones that haven't a default open command defined) are now
opened by my app by default which was not my intention :-(
Is there a workaround to that?

Try changing the registry key name from "Open" to something else.

Dave

 

[David Lowndes]

Thank you, David. The thing with the registry worked but now unassigned

filetypes (the ones that haven't a default open command defined) are now
opened by my app by default which was not my intention :-(
Is there a workaround to that?

Try changing the registry key name from "Open" to something else.

Dave

 

[cody]

Try changing the registry key name from "Open" to something else.

No, I didn't used "open" for my key. But nevertheless my shellhandler gets
the default action (double-click on a file), when this file type has no
assigned default action (That means all "unknown" filetypes are now opened
by my application).

 

[cody]

Try changing the registry key name from "Open" to something else.

No, I didn't used "open" for my key. But nevertheless my shellhandler gets
the default action (double-click on a file), when this file type has no
assigned default action (That means all "unknown" filetypes are now opened
by my application).

 

[David Lowndes]

Try changing the registry key name from "Open" to something else.

No, I didn't used "open" for my key. But nevertheless my shellhandler gets
the default action (double-click on a file), when this file type has no
assigned default action (That means all "unknown" filetypes are now opened
by my application).

Can you show us the registry branch settings that you have for your
association.

Which OS's have you tried this with? I note that the PSDK
documentation mentions that the first registry key will be the default
for versions of the shell >= 5, but that didn't seem to happen when I
tried it on XP - but I might be doing something subtly different.

There's more in-depth information in the PSDK documentation section
"Creating a File Association" on MSDN.

Dave

 

[David Lowndes]

Try changing the registry key name from "Open" to something else.

No, I didn't used "open" for my key. But nevertheless my shellhandler gets
the default action (double-click on a file), when this file type has no
assigned default action (That means all "unknown" filetypes are now opened
by my application).

Can you show us the registry branch settings that you have for your
association.

Which OS's have you tried this with? I note that the PSDK
documentation mentions that the first registry key will be the default
for versions of the shell >= 5, but that didn't seem to happen when I
tried it on XP - but I might be doing something subtly different.

There's more in-depth information in the PSDK documentation section
"Creating a File Association" on MSDN.

Dave

 

[cody]

Can you show us the registry branch settings that you have for your
association.

Which OS's have you tried this with? I note that the PSDK
documentation mentions that the first registry key will be the default
for versions of the shell >= 5, but that didn't seem to happen when I
tried it on XP - but I might be doing something subtly different.

There's more in-depth information in the PSDK documentation section
"Creating a File Association" on MSDN.

Thats what I did:

[HKEY_CLASSES_ROOT\*\Shell\FileInfo\command]
@="C:\\programme\\FileSearch\\filesearch.exe -t \"%1\""

I'm using Windows2000/Service Pack 4

--
cody

Freeware Tools, Games and Humour
http://www.deutronium.de.vu
[noncommercial and no ****ing ads]

 

[cody]

Can you show us the registry branch settings that you have for your
association.

Which OS's have you tried this with? I note that the PSDK
documentation mentions that the first registry key will be the default
for versions of the shell >= 5, but that didn't seem to happen when I
tried it on XP - but I might be doing something subtly different.

There's more in-depth information in the PSDK documentation section
"Creating a File Association" on MSDN.

Thats what I did:

[HKEY_CLASSES_ROOT\*\Shell\FileInfo\command]
@="C:\\programme\\FileSearch\\filesearch.exe -t \"%1\""

I'm using Windows2000/Service Pack 4

--
cody

Freeware Tools, Games and Humour
http://www.deutronium.de.vu
[noncommercial and no ****ing ads]