Developer Playground started out as an idea for an application to trace any program's runtime behavior. Jonas had previously built ComTrace, but felt it was time to conquer non-COM apps as well.
So, we started thinking, and this is what we came up with. A developer's playground, with the following functionality:
Developer Playground can only monitor interactions between a process and its loaded DLLs, and between DLLs within a process, but can't give any more detailed information about calls within the .EXE or within DLLs. Nevertheless, it is a powerful tool in the hands of a developer.
Typical usage would involve:
Spelunking — If you're ever curious what goes on behind the scenes, and why Windows is not behaving the way you'd expect it to, fire up Developer Playground and find out at least what the call-chain looks like.
Debugging — Do you have a problem that only manifests itself on some machines? No matter how much debug logging you add, you can't seem to track it down? Developer Playground shows you the program flow without your having to add specific debugging code or single-step through optimized assembly code.
Reverse-engineering — Are you trying to mimic functionality you've seen somewhere, but you can't figure out how they did it? Trace the target application and find out.
In order to run Developer Playground you need either of the following operating systems:
Version 1.1 — 2003-09-28
Version 1.0 — 2003-08-28 — First public release
Known issues in the latest version:
| Description | Status |
| Excessive screen flicker with Find/Find Next | Fixed, under test |
| Can't hook export forwarders | Investigating |
| Check for DEPENDS.EXE existence only works if no path is specified | Fixed, under test |
| Context-menus only work as expected when DP is located on primary display | Fixed, under test |
Click here to download an installer for Developer Playground. Execute the downloaded binary to install.