[windev] App Paths, ShellExecute, CMD box...

[Serge Wautier]

App Paths is a ShellExecute() thingie. 
Cmd.exe doesn't use ShellExecute(), it goes straight to CreateProcess(),
which doesn't know about App Paths, as confirmed here:
<http://msdn.microsoft.com/en-us/library/ms682425.aspx>


Serge.
http://www.apptranslator.com



> -----Original Message-----
> From: windev-bounces at windev.org [mailto:windev-bounces at windev.org] On
> Behalf Of David Little
> Sent: vendredi 3 avril 2009 19:05
> To: Windows Developers (Mailing List)
> Subject: [windev] App Paths, ShellExecute, CMD box...
> 
> I'm putting a bunch of common files in a common folder - mostly it's
> resources like menus, icons, etc. - and in the install, I write the
> value of the common files folder to the app path key at:
> 
> 
> 
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
> Paths\<appname>.exe\Path
> 
> 
> 
> Pretty standard stuff, except I noticed that none of my resource are
> updated if I start the .exe from a command prompt.   Searching for "app
> path" and cmd.exe is pointless.  Any ideas?
> 
> 
> 
> Thanks!
> 
> 
> 
> -          David Little
> 
> -          Houston, TX
> 
> 
> 
> 
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.windev.org/pipermail/windev/attachments/20090403/8fdb2d84/
> attachment.htm
> --
> Windev mailing list at Windev at windev.org
> 
> Lost your password?  Need to unsubscribe or change your delivery
> options?
> Go to http://lists.windev.org/mailman/listinfo/windev
> --
> Search the Windev Archives - www.windev.org