|
OK, I have been banging my head several times to get this working. Now here it is for your reference.
Here are the steps to debug a WF-based workflow hosted in ASP.NET. - Enable debugging for your ASP.NET application by setting 'debug=true' in the web.config
- Set the workflow library as the startup project and set appropriate breakpoints on the workflow
- In the workflow project's properties dialog select the 'Debug' tab and choose 'Start with external URL'. Enter the URL of your default webpage here
- Now attach to w3wp.exe (on Server 2003, Vista), aspnet_wp.exe (on XP) or webdev.webserver (when using Cassini-like dev and test web server from Visual Studio 2005) in which the workflow is ultimately running - set the debug engine to “Workflow”
-
- Open 'Attach to Process...' dialog
- Click the 'Select...' button next to the 'Attach to...' textbox
- Select the option 'Debug these code types' and only check 'Workflow'
- Open the default web page in a browser and trigger the workflow.
Now you should be able to debug your ASP.NET-hosted WF workflows. Hope this helps.
|