How "safe" (from a best practice and supportability perspective) is the use of DLL injection techniques?

Another question in internal discussion.

Here is one reply:

---

From:
Subject: RE: DLL Injection

DLL injection is never safe. You're talking about squirting code into a process that was never designed, built, or tested by the process's author, and co-opting or creating a thread to run that code. You run the risk of creating timing, synchronization, or resource issues that weren't there before or exacerbating issues that were there.

Comments

• Anonymous
  February 19, 2004
  And yet this is something some companies are forced to do every day, as a matter of practice, due to lack of extensibility in the platform. It's been happening for at least a decade.
• Anonymous
  February 19, 2004
  Do you know the reason why those companies opt to use this technique? Just curious.
• Anonymous
  February 20, 2004
  The comment has been removed
• Anonymous
  May 06, 2004
  How to use PerformCallBack4? because this function have structure CALLBACKINFO and what parameter LPVOID1 , LPVOD2 ,..