Hello,
I'm working through the Hands on Lab (HOL) #1 for WF Beta 2, Exercise 3 and task 7. Everything's been working according to the lab instructions until I got to the debugging section. I'm seeing a couple of strange things:
1. Step 6 tells me to step into the code for the ReportSubmitted_Invoked handler. I've tried this, but the debugger doesn't go to the code level; it simply highlights the next activity in the workflow designer. I also tried explicitly setting a breakpoint in the ReportSubmitted_Invoked method of the code beside file, but it's not hit and appears disabled. The text 'ReportSubmitted_Invoked' is written to the console, however so the code is being executed.
2. There's a picture after step 6 which shows how the workflow should look at this stage in debugging. We're asked to stop when we come to the rejectedExpenseReport1 activity. However, I don't see the rejectedExpenseReport1 activity when debugging! Instead what I see is several other activities in the second branch of the IfElse activity, activities that I did not explicitly add and do not appear in the WF designer when not debugging (but authoring the workflow). I assume the debugger is expanding the (presumably) composite rejectExpenseReport1 activity to show its child activities...
Please clarify. Thanks,
Notre
Beta 2 Debugging question for HOL 1
kg81
Hi Sonali,
Thanks for your reply. The breakpoint that's hit (the activity level breakpoint in the WF design surface) is bound. The code level one appears as unbound.
As per the HOL exercise instructions, I am setting the startup application from the project to a test host provided as a lab resource. This is set as an external program. Please see steps 1-6 of task 6, exercise 3 in Hands On Lab #1 for details.
Notre
solmyr72
Hi Sonali,
All the files are in the specified folder. I looked at the list of modules when debugging and the symbols are loaded for ExpenseActivities.dll, ExpenseHost.exe, and ExpenseLocalServices.dll. For these, the symbols are all loaded from the Lab1 resources path.
In the case of ExpenseWorkflows.dll, the symbols are not loaded. ExpenseWorkflows.dll is being loaded from the resources path, not the path where I've created the workflow. I think this is the problem. How do I get my assembly to load, rather than the one in the lab resources path
Notre
Herru Perdana
Notre: Are the breakpoints on the designer surface displayed as bound breakpoints or are they displayed as unbound (hollow circles with exclamation mark). If yes, you are facing same problem mentioned here
http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=219557&SiteID=1
-Sonali
Carl-Otto
Hi Notre,
Breakpoints can be unbound if symbols are not loaded. Please check if the files
1. ExpenseActivities.pdb
2. ExpenseLocalServices.pdb
3. ExpenseWorkflows.pdb
are present in the folder ExpenseWorkflows\ExpenseWorkflows\bin\Debug. you can also set the path for the symbol files in
Tools\Options\Debugging\Symbols\symbol file locations
I tried debugging the ExpenseWorkflows.sln in the Completed\Exercise3 and I was able to debug as per the instrcutions.
If this does not help, please share your solution and I will try to take a look.
-Sonali
Philip Galea
Hi Notre,
Please check the directories that the projects in your solution are located in. You should also check the references between projects. You should find somewhere a reference to the resources directory instead of your project - change it.
Regards,
Paul
fleacricket
I finally figured out what was going wrong. I was pointing to the wrong ExpenseHost.exe in the external program to start for debugging. I was pointing to the one in the resources folder, rather than my working folder. So, when my the CLR probed for ExpenseWorkflows.dll, it started in the wrong directory and found a matching assembly, but not the one I intended to use. After making this change, I was able to step into the C# code and the workflow debugging experience matched the HOL pictures.
Notre