One of the oldest tricks you as a developer can pull is using the print statement in expression shapes in an orchestration at critical points. This can be done by using the .NET System.Diagnostics.Trace and System.Diagnostics.Debug class libraries. You can use these libraries to write trace and debug information to one or more listeners like DebugView for instance. With this tool you can monitor debug output on your local system or on any computer on the network that you can reach via TCP/IP.
Another way of debugging similar to System.Diagnostic is log4net. Log4net is a port of the log4j framework to the .NET runtime and part of the Apache Logging Services project. This project is intended to provide cross-language logging services for purposes of application debugging and auditing. It is a tool that helps the programmer output log statements to a variety of output targets. It can enable to track orchestration events, without using the orchestration debugger and can be viewed as a substitute for it. The following resources can be used to download the tool, find guidance in usage and background information:
Steef-Jan Wiggers edited Revision 16. Comment: Minor edit
Steef-Jan Wiggers edited Revision 13. Comment: Minor edit
Steef-Jan Wiggers edited Revision 10. Comment: Adjusted text
Steef-Jan Wiggers edited Revision 9. Comment: Added topics and resource links
Steef-Jan Wiggers edited Revision 7. Comment: Added text
Steef-Jan Wiggers edited Revision 6. Comment: Added text
Steef-Jan Wiggers edited Revision 5. Comment: Formatting
Steef-Jan Wiggers edited Revision 4. Comment: Added resource link
Steef-Jan Wiggers edited Revision 3. Comment: Added text
Steef-Jan Wiggers edited Original. Comment: Added note