You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,9 @@ Inject any DLL into any running process with ease! Injector is a command line to
12
12
13
13
You may use it in you post-build events in Visual Studio to save time and take away complexity of code by "outsourcing" the injection process. You may of course use it for any othe scenario which comes on your mind. Check out the possible command line arguments:
14
14
15
-
-`-n|--process-name` identifies the target process by it's module name
16
-
-`-w|--window-name` identifies the target process by it's main windows name
17
-
-`-p|--process-id` identifies the target process by it's PID
15
+
-`-n|--process-name` identifies the target process by its module name
16
+
-`-w|--window-name` identifies the target process by its main windows name
17
+
-`-p|--process-id` identifies the target process by its PID
18
18
-`-i|--inject` or `-e|--eject` specifies the action to perform (inject or eject the DLL)
19
19
20
20
Then simply append one or more absolute (or relative) path(s) of the DLL to be in-/ejected.
0 commit comments