I recently had to develop a SharePoint workflow, and I made sure that the experience is very plausible for the most painful programming task that I have ever had to solve. One big problem that I encountered was the problems that I encountered when I had to go through it in the debugger.
Here's an article on how to debug a SharePoint workflow here , which explains how to set breakpoints, etc. This involves copying the .pdb file to the GAC along with the DLL file containing your workflow. You must do this from the command line (or batch file) because Windows Explorer does not allow you to view the corresponding subdirectory c: \ windows \ assembly.
However, if you do this, the next time you try to deploy a workflow from Visual Studio, it complains that it cannot be deployed because the file cannot be signed, and if you try to copy the new version of the dll to the GAC, it reports to you that the .dll file is locked.
I found that you can work around this for some time by running iisreset, but in other cases you need to restart Visual Studio, and there were frequent times when I even had to restart the computer in general because some secret process blocked the file. On the other hand, when I do not use the debugger, everything works fine.
Does anyone know of an easier way to debug workflows than this?
source
share