When developing a workflow, I encountered a lot of low-level problems and wasted a lot of time. I will record them here for future reference.
- There are often some inexplicable problems, such as the failure of breakpoint debugging (including other aspx) for workflows and the failure of applications for new workflows. At this time, IIS has not updated the. NET cache. The solution is to delete files in c: \ windows \ Microsoft. NET \ framework \ v2.0.50727 \ temporary ASP. NET files.
- Some times the DLL has been updated, but it is not automatically updated to GAC. Copy it manually.
- Remember to keep the details of the items in the workflow as much as possible. Otherwise, the entire DLL is updated every time, which takes a lot of time.
- Developing workflows requires high machine performance (especially when debugging). It is best to build a better machine.
- If you cannot obtain the specific error information during vs design, iisreset first, delete the cache in 1, restart vs, and re-open the WF design interface to re-compile.
- When uninstalling An ASPX form workflow, remember 1. Delete the workflow instance appended to the list (the generated task is automatically deleted here ). 2. Delete the content type appended to the task list. 3. Run the delete script and iisreset.
- Install a workflow with the content type. 1. Run the installation script. 2. Add the content type to the task list. 3. Add a Workflow
- If the content type is not updated, you can directly press F5 to update the workflow.
- Remember not to use auto-appended workflows. This auto-appended workflow has many problems (especially when there is an initialization form ).
- Try to use F5 to debug the workflow. When a process is appended, errors that cannot be debugged in step 1 may often occur.
- In some cases, an error occurs in the parent container of the workflow. In this case, check the designer. CS file.
- Define variables for all nodes in the workflow as much as possible. Do not use attributes. The variable can be assigned a value to the next node. The attribute does not seem to be allowed.
- Set callstack = "true" in the web. config file of the site so that you do not have to check logs every time an error occurs. The page displays the specific error information.
