I know the calls are going out, as I've used an incremented variable to track it. But some just never make it to the output window. Is this a known issue? Is there a workaround?
Similarly, breakpoints in the workflow are very unreliable. Stuck with this?
For brakepoints to work you need to make your workflow project the startup project. If it's a dll use the debug startup application to get it running.
No clue about the Debug.WriteLine. Could it be the trace listener is dropping data because of multi threaded locking?
On the issue with break points not being hit, it usually is because the refactoring folder (obj folder) is out of sync with the workflow designer. One way around this is to close Visual Studio completely (all instances if you run several like me), then in Windows Explorer navigate to your project folder and delete the obj folder. Then open up your solution again and do a re-build.
I've had that happen to me several times, and the way around it was the above trick.