Dehydration & Rehydration in WF

If we have a long running workflow tasks or have a  large number of workflow tasks executing , we can unload and store it in a temporary storage using Persistence services ships with Workflow Foundation.

Dehydration : Removing a workflow instance from execution status and storing it away for later recall is called Dehydration. Typically persistence services that comes with WF is used for this purpose, but you can write your own service to perform the same task.

Rehydration: When needed – the workflow instance is brought back from persistence service. The process of bringing it back into an execution status is known as Rehydration.

The main goal is to unload the long running tasks from memory and store then in temporary storage and retrieve it when its needed. And by this way – it’s possible to provide efficient memory utilization.

Interface 101: Explicit Interface Implementation using C#

The primary motivation of introducing inerface is to enforce OO-style of thinking while revoking the drawbacks of multiple inheritance. In fact, the support for explicit interface implementation is an important tool in OO-developers’ toolbox. Utilizing this concept, we can implement multiple interfaces in a class, and still no ambiguity gets introduced.

In fact, explicit interface implementation ensures private accessibility via interface reference. That is, in order to access any member of a class that implements an interface explicitly, an interface reference is required, which supports the concept called “Run-time Bindings“, and introduces a higher level of abstraction.

In the rest of the post we focus on following–

glyphicons Defining interfaces,
glyphicons Implementation of the interfaces explicitly,
glyphicons Advantages of explicit interface implementation.

To do so, we start by defining interfaces and shows how to apply explicit interface implementation using an example. Please note that, this is a simple and contrived example, intended only to be illustrative.

public interface ISimpleCalculator{
int Add(int num1, int num2);
public interface ICalculator{
double Add(double num1, double num2);

The following class Calculator implements both interfaces using explicit interface implementation.

public class Calculator:ISimpleCalculator,ICalculator{
int ISimpleCalculator.Add (int num1, int num2)
return num1 + num2;
double ICalculator.Add (double num1, double num2)
return num1 + num2;
view raw gistfile1.cs hosted with ❤ by GitHub

Now that we have implemented these interfaces, next we see outlines several examples to show how to use this implementation. The first example below tries to use the Add method without interface reference.

Calculator calc = new Calculator();
calc.Add(); // Uncomment it to get the Compile time Error
view raw gistfile1.txt hosted with ❤ by GitHub

Therefore, it gets a compile time error as the implementation is private and can only be accessed via interface reference as follows.

ISimpleCalculator simpleCalc = calc;
int result = simpleCalc.Add(5, 10); // returns 15
view raw gistfile1.txt hosted with ❤ by GitHub

As we have notice that the both interfaces have Add as a member. In fact, Calculator class also implements both Add method via polymorphic references. Next example shows how to invoke ICalculator.Add by using an instance of Calculator.

ICalculator floatingNumberCalculator = calc;
floatingNumberCalculator.Add(3.2 ,5.8);
view raw gistfile1.cs hosted with ❤ by GitHub

To sum up, the key take-aways from this discussion regarding explicit interface implementation are as follows.

glyphicons It make the whole implementation Abstract/Private . That is , you need the interface reference to access that implementation.

glyphicons It allow you to implement multiple Interface and at the same time, does not introduce any ambiguity. So, the polymorphic reference or runtime binding can be implement very efficiently.

We highly appreciate any comment or query regarding this post. Thanks!

See More


[R-1: 02-04-2013] Updated formatting to make this post more consistent with current CSS.

MethodImplAttribute -Easy way to Synchronize

Sometimes when we try to synchronize a method of a .Net class we need to consider lots of stuff. And sometimes it really becomes complicated to synchronize a method.  But if we come to a conclusion that only one thread will be accessing a particular method at a single point of time then there is a really faster way to Synchronize it –

Using attributes of System.Runtime.CompilerServices namespace , we can change runtime behavior of CLR. MethodImplAttribute is one of such kinda attribute by using which CLR can be notified how the method was implemented. MethodImplAttribute accepts one parameter called MethodImplOptions.

MethodImplOptions has one field – MethodImplOptions.Synchronized that actually tells the compiler only one thread can access the method at any point of time. This is like lock keyword but only difference is that here we are locking the whole method. Let’s have look at one simple example –

public class DemoMethodImpl
     public void MethodToSyncronize()