tag:blogger.com,1999:blog-61099024283945912352024-09-09T11:25:32.387+05:30Vikas Goyalnoreply@blogger.comBlogger9125tag:blogger.com,1999:blog-6109902428394591235.post-14654162287026913252008-10-02T23:10:00.001+05:302008-10-02T23:10:32.646+05:30

Now that features of .NET 4.0 have started becoming officially public… I am also happy to start blogging about them. Based on the available info.. here is the link containing the new features coming out in .NET framework 4.0. What’s new in .net framework 4.0 I will be updating this link on regular basis .. so bookmark it.

Vikas Goyalnoreply@blogger.com0tag:blogger.com,1999:blog-6109902428394591235.post-69879055336043534302007-02-27T11:56:00.001+05:302007-09-18T12:56:01.653+05:30

In this post i will demonstrate how to build a basic state machine workflow. A state machine workflow consists of set of states with one state marked as 'start' state and one as 'final' state. Every state has an event associated with it and based on those events, workflow transitions from one state to another. It always starts from 'start' state and once it reaches the 'final' state, the workflow

Vikas Goyalnoreply@blogger.com3tag:blogger.com,1999:blog-6109902428394591235.post-10163123665021082992007-02-21T17:54:00.001+05:302007-09-18T12:46:59.521+05:30

Windows Workflow foundation provides lot of services which can be plugged into workflow runtime based on the requirement. This reduces the overhead on runtime by having lot of services loaded without being used. These services come by default implementations but are fully extensible. The main services which come with framework are : Scheduling Services : This is to manage how workflows are

Vikas Goyalnoreply@blogger.com0tag:blogger.com,1999:blog-6109902428394591235.post-64790809478228665862007-02-21T12:21:00.001+05:302007-09-18T12:46:37.180+05:30

This tutorial covers following : Creating a Sequential workflow using code-separation authoring mode Use Visual Studio 2005 and Windows Workflow Foundation extensions for VS Demonstrates IfElse activity and rule based condition authoring To start follow the first three steps as in following post. In the next step drag and drop the IfElse activity on to the empty workflow file. The

Vikas Goyalnoreply@blogger.com1tag:blogger.com,1999:blog-6109902428394591235.post-45554073165583370202007-02-20T15:50:00.001+05:302007-09-18T12:46:06.893+05:30

If you are new to WF pls read my previous posts on WF before proceeding with this. In this post i will cover following : How to use IfElse Activity in sequential workflow provided by WF framework Authoring conditions using code instead of declarative rules. To start follow the first three steps as in following post. In the next step drag and drop the IfElse activity on to the empty workflow

Vikas Goyalnoreply@blogger.com0tag:blogger.com,1999:blog-6109902428394591235.post-69368156949702453402007-02-20T15:46:00.001+05:302007-09-18T12:04:34.902+05:30

Most of the workflow we see in our daily lives are multi path which means based on different condition they take different path before getting completed. Be it a financial workflow like Funds Transfer happening in Corporate environment which based on amount goes to different approvers or a non-financial workflow like leave approval in an enterprise which goes to different approver based

Vikas Goyalnoreply@blogger.com0tag:blogger.com,1999:blog-6109902428394591235.post-65698176331975330052007-02-15T15:23:00.001+05:302007-09-18T10:56:40.046+05:30

This post gives step by step details on how to build a simple sequential workflow using Code Activity. It assumes that all the components required to develop workflow apps have been installed. List can be obtained here. Step 1 : Create an empty workflow project in VS 2005. Empty project helps in understanding the architecture of app better as we build from scratch. Step 2 : As we will

Vikas Goyalnoreply@blogger.com0tag:blogger.com,1999:blog-6109902428394591235.post-86312103510618493202007-02-15T11:49:00.001+05:302007-09-18T10:55:34.537+05:30

Here is a list/link to components which are required to develop/run windows workflow enabled applications : Microsoft Windows SDK for .NET Framework 3.0 : contains Workflow runtime/engine and libraries Microsoft Visual Studio 2005 : IDE for building WF applications Microsoft Visual Studio 2005 Extensions for Windows WorkFlow Foundation : add-on to Visual Studio 2005,

Vikas Goyalnoreply@blogger.com0tag:blogger.com,1999:blog-6109902428394591235.post-42575398938450066752007-02-09T10:40:00.001+05:302007-09-18T10:53:32.975+05:30

With .NET 3.0, Microsoft released a new infrastructure for developing, deploying and maintaining workflow aware applications. The .NET 3.0 composition can be expressed as below : .NET 3.0 = .NET 2.0 + WCF + WPF + WF + CardSpace WCF is Windows Communication Foundation for distributed computing, WPF is Windows Presentation Foundation for building interactive UI, WF is Windows Workflow Foundation

Vikas Goyalnoreply@blogger.com0