http://developers.de/blogs/damir_dobric/archive/2008/06/11/problem-with-debugging-of-workflows.aspxWhile working with workflows you may have noticed, that sometimes it is not possible to stop the workflow in debugger. More precisely, the workflow can be stopped in debugger as long the breakpoint is set in code-behind, but not if the breakpoint is setenCommunityServer 2008 SP1 (Build: 30619.63)http://developers.de/blogs/damir_dobric/archive/2008/06/11/problem-with-debugging-of-workflows.aspx#1960Wed, 11 Jun 2008 21:58:49 GMT7e491611-45ad-4dae-a68f-c4cb64439510:1960Mark Simms<p>Damir,</p> <p>One other useful way of doing this (especially running in an environment with multiple application host processes) is to:</p> <p>1. Open the appropriate solution or project in visual studio.</p> <p>2. Temporarily embed a System.Diagnostics.Debugger.Launch() in the startup code for the module (perhaps wrapped in an #if DEBUG conditional) and launch the host.</p> <p>3. From the list of debuggers that will appear, select the one with the project or solution open.</p> <p>Same outcome, may be a little smoother depending on your development setup (I usually do this for debugging new event handlers for Biztalk RFID).</p> <p>Mark</p> <div style="clear:both;"></div><img src="http://developers.de/aggbug.aspx?PostID=1960" width="1" height="1">