Talk:Send ShellExtension: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m →Hardcoded Windows Path: %SystemDrive%, linked to source |
||
| Line 14: | Line 14: | ||
== Hardcoded Windows Path == | == Hardcoded Windows Path == | ||
It's nice to see that you copy the file into the correct windows directory... but what about the .reg? not all ppl have their windoze @ c:\ [[User:Slash|Slash]] 21:56, 29 March 2009 (UTC) | It's nice to see that you copy the file into the correct windows directory... but what about the .reg? not all ppl have their windoze @ c:\ [[User:Slash|Slash]] 21:56, 29 March 2009 (UTC) | ||
Using %SystemDrive% instead of hard-coding should fix that problem. This works for Windows NT-based versions (XP/Vista/7), according to what Wikipedia says[http://en.wikipedia.org/wiki/Environment_variable] --[[User:HACKhalo2|HACKhalo2]] 17:55, 15 April 2010 (UTC) | |||
Latest revision as of 19:55, 15 April 2010
I think that this is not really a shell extension. I am quite sure that shell extensions need to be implemented in a dll.--henke37 13:10, 3 June 2008 (PDT)
- Well what would you call it then? It extends the functionality of the shell for a certain file type. The only difference is it uses built-in registry based menu topology instead of loading something else to do more complicated things. It WORKS, doesn't it? ProdigySim 14:18, 3 June 2008 (PDT)
For me it isn't setting the WIILOAD environment var --Bool 02:53, 24 June 2008 (CEST)
"it doesnt set the variable"
Correct, due to bad testing :P
New version underway
Hardcoded Windows Path
It's nice to see that you copy the file into the correct windows directory... but what about the .reg? not all ppl have their windoze @ c:\ Slash 21:56, 29 March 2009 (UTC)
Using %SystemDrive% instead of hard-coding should fix that problem. This works for Windows NT-based versions (XP/Vista/7), according to what Wikipedia says[1] --HACKhalo2 17:55, 15 April 2010 (UTC)