Comments on: Programming Pitfalls: Off the beaten PATH http://www.opencandy.com/2010/03/31/candywrap-1-process-spawning-rundll32-the-path-variable/ Thu, 13 Oct 2011 07:31:02 +0000 hourly 1 http://wordpress.org/?v= By: CandyPicks #1: Rapid Environment Editor, freeware Windows environment variables editor | Helping Software Developers and Users - OpenCandy http://www.opencandy.com/2010/03/31/candywrap-1-process-spawning-rundll32-the-path-variable/comment-page-1/#comment-81 CandyPicks #1: Rapid Environment Editor, freeware Windows environment variables editor | Helping Software Developers and Users - OpenCandy Fri, 09 Apr 2010 21:06:58 +0000 http://www.opencandy.com/?p=2020#comment-81 [...] week ago, my colleague Adrian wrote a CandyWrap article intended primarily for developers about Rundll32.exe and the system PATH environment [...] [...] week ago, my colleague Adrian wrote a CandyWrap article intended primarily for developers about Rundll32.exe and the system PATH environment [...]

]]> By: Adrian http://www.opencandy.com/2010/03/31/candywrap-1-process-spawning-rundll32-the-path-variable/comment-page-1/#comment-54 Adrian Wed, 31 Mar 2010 21:44:15 +0000 http://www.opencandy.com/?p=2020#comment-54 John, Good question. This is done because the DLL needs to be capable of running even if the calling process ends, ie. asynchronously and in it's own process. John,

Good question. This is done because the DLL needs to be capable of running even if the calling process ends, ie. asynchronously and in it’s own process.

]]> By: John Kelley http://www.opencandy.com/2010/03/31/candywrap-1-process-spawning-rundll32-the-path-variable/comment-page-1/#comment-53 John Kelley Wed, 31 Mar 2010 20:49:43 +0000 http://www.opencandy.com/?p=2020#comment-53 Can you explain your choice of _spawn over the traditional LoadLibrary/GetProcAddress? It's rather strange to spawn a new process just to call a DLL export unless you're being extremely paranoid and don't want the DLL being loaded into your address space. Can you explain your choice of _spawn over the traditional LoadLibrary/GetProcAddress?

It’s rather strange to spawn a new process just to call a DLL export unless you’re being extremely paranoid and don’t want the DLL being loaded into your address space.

]]>