workflow-foundation

Currently we have a sequential workflow in sharepoint 2010 that has a delay activity. The delay is set to five minutes. The workflow checks on the status of five tasks and depending on the results, it either delays or completes. I have a workflow history log item set to write right before the delay and right after the delay. Sometimes the delay does not fire, an example would be as follows: Delay activity fires every five minutes for 3 full days on one item, then for no particular reason it fails to wake up for 17 hours...then fires and completes. Any ideas? I have verified all of the timer

MSBuild in TFS 2010 has been replaced by Windows Workflow 4.0. It means when you are creating a Build Definition, you won't have a TFSBuild.proj to edit instead you must edit a workflow to customize your build. BTW am I correct if I say Microsoft is not supporting MSBuild in TFS 2010 and learning MSBuild as a TFS 2010 Team Build administrator doesn't worth? And another more question: is Microsoft going to replace Visual Studio Projects' language from MSBuild to something like Windows Workflow? Jim Lamb I'm the Program Manager for the build automation features of TFS, so I'd like to comment on

I am trying to host a WF4 (RC) Service dynamically. I have a test solution with two projects. The first is a declarative workflow service library with one root Flowchart activity in it, and a simple custom code activity. The workflow service library does not depend on any other custom assemblies or references. The second is my host app, which in my test solution is just a console application. In my host app, I am attempting to the use ActivityXamlServices to load the Xaml for the workflow service into an activity, and then use the WorkflowServiceHost to fire up a workflow instance using that

Can anyone explain what is windows workflow and how can we use in the work organization. Windows Workflow Foundation is a fascinating concept. It allows you to create powerful applications (or just parts of them) using a combination of flowchart-like concepts and normal code. The deeper value of this may not be immediately obvious. Say you're building a large e-commerce site. Over time, your workflows for processes such as fulfillment will change radically. The code will eventually become a horrid cludge of ideas shoehorned over old ideas. You will be forced to work up reams of documentation

Is it possible to use DI in your workflow activities? and if yes, how? For example if you have an activity like public sealed class MyActivity : CodeActivity { public MyClass Dependency { get; set; } protected override void Execute(CodeActivityContext context) { Dependency.DoSomething(); } } how can i set Dependency ? (I'm using Spring.Net) Workflow doesn't use an IOC container. It uses the ServiceLocator pattern where you add dependencies to the workflow runtime as extensions and workflow activities and retrieve these services from the workflow extensions through the context. A ServiceLocator

Currently we have thousands of Microsoft Word files, Excel files, PDF's, images etc stored in folders/sub folders. These are generated by an application on a regular basis and can be accessed at any time within that application. As we look to upgrade we are now looking into storing all these documents within SQL Server 2005 instead. Reasons for this are based on being able to compress the documents, adding additional fields to store more information on those documents and applying index’s where necessary. I suppose what I’m after is the pros and cons of using SQL Server as a document

Pre-warning : There are some other questions similar to this but don't quite answer the question (these include: Alternatives to Windows Workflow Foundation? , Can anyone recommend a .Net open source alternative to Windows Workflow? ) We are developing a system that is an event based state machine, currently we are investigating windows workflow, our system needs to be low latency in its response to events from a multitude of sources (xmpp, http, sms, phone call, email etc etc) coming into the system, scalable and resilient and most importantly customisable. For a variety of reasons (and due