Integrating workflow into ASP.NET applications means communicating with activities via a workflow queue and hosting the runtime in the global application class. We'll show you how.
MSDN Magazine January 2009
View Complete Post
The heart of Windows Workflow Foundation is its declarative programming model. Here are some best practices to consider when using WF to realize software solutions in the real world.
MSDN Magazine December 2008
Here is an ASP.NET AJAX data-driven Web application that takes the best features from server- and client-side programming to deliver an efficient, user-friendly experience.
Bertrand Le Roy
MSDN Magazine October 2008
The Compact Framework Control class doesn't provide direct access to Windows messages. However, with P/Invoke, a few lines of native code, and the Compact Framework MessageWindow class, it's still possible to access underlying Windows messages. This can be used to work around any .NET Framework features, including keyboard support, that are not included in the Compact Framework.
MSDN Magazine April 2004
MSDN Magazine February 2004
Microsoft Exchange 2000, the upcoming version of Exchange Server for Windows 2000, provides many new features including integration with Active Directory, Web Storage System events and forms, and a new version of Collaboration Data Objects (CDO). Exchange 2000 also provides a workflow engine and design tool to create workflow applications. This article will give you an overview of these new features and looks at ways to do a few standard tasks with the new version of CDO. Also included is a sample workflow application that manages the posting of messages to a public server to illustrate the new workflow engine and workflow design tool.
MSDN Magazine July 2000
In SharePoint 2010, I'm starting workflow #2 programatically from my workflow #1. See code below:
SPList currentList = web.Lists[new Guid(ListId)];
SPListItem currentListItem = currentList.GetItemById(ListItem);
//resolve any lookup parameters
string workflowId = base.ProcessStringField(WorkflowIdentifier);
//find workflow association by name
SPWorkflowAssociation workflowAssoc = currentList.WorkflowAssociations.GetAssociationByName(workflowId, Thread.CurrentThread.CurrentCulture);
if (workflowAssoc != null)
//start the workflow
SPWorkflow workflow = site.WorkflowManager.StartWorkflow(currentListItem, workflowAssoc, workflowAssoc.AssociationData, SPWorkflowRunOptions.Synchronous);
And workflow #2 will hang with Starting status (1-10 minutes), Then the workflow #2 status would be modified to Completed.
I couldn't find how to start the workflow # 2 immediately and complete immediately without several minutes delay
I have a serial approval workflow created out of the box. The setting cancell this workflow when the document is rejected is selected. But if one of the approvers rejects it the workflow keeps running. After this is it will give acces denied errors for the
So for example what is happening. The workflow is started and sends a email to persone 1. This persone approves so the workflow sends a email to persone 2. Persone 2 decided to reject the document. Now i want the workflow to be cancelled, but it
keep running and sends a email to persone 3 for approval. If persone 3 opens the workflow he get's a acces denied error, i guess because of the reject.
Anyone has a idea what is happening here?