[Vancouver]

You can backup the old csc.exe, write a csc.exe that dumps the parent process's name (and possible stack trace if you know how to walk a stack) to the event log before calling the old csc.exe with all arguments, and put the new csc.exe in the place of the old csc.exe. This way you can find out who is calling the exe.

http://social.msdn.microsoft.com/For...3-8dc8af28f50c