Data logging using Enterprise Logging App block.

One of my developer had been working for 3 days now to figure out the mechanism to write the logs into database using Logging Application Block 5.0.

So I had to look it,so that the issue would not linger anymore..

Following are the things I did to figure it out

  1. Downloaded the Enterprise library documentation from here and persused the section “Logging to a Database” under “The Logging Application Block”
  2. Got good insight on what to do, so followed the steps mentioned in the documentation.
  3. Stumbled on a generic “Activation error”, After researching online for a while, Realized that it is a known issue and I need to do the workaround as mentioned in the below links


BizTalk Tracing Matrix with different components

You guys may have already seen this, but this article has some great information in regards to performance considerations when setting up tracing capabilities in BizTalk solutions.  The following chart is from the article.  They were comparing the ETW Framework with Log4Net, Enterprise Library and the .Net System.Diagnostics.Trace.Component.


Microsoft Application Infrastructure Technologies.

Being a BizTalk Evangelist, It makes me happy to se BizTalk Server is standing audaciously alongside “Server AppFabric” and “Azure AppFabric”.


Click here to know what I am talking about!

Click here to read more about Middleware from Microsoft



Pricing and Licensing

BizTalk Server

Enterprise : $44,228

Standard : $10,138


Volla No Cost?

Windows Server AppFabric is free, so there’s no licensing ‘cost’ involved – it’s treated as an add-on to Windows/the .NET framework. The Azure AppFabric SDK does come with a license which states what you can redistribute, but the licence screen in the Windows Server AppFabric installer refers you to the Windows license.

However, while AppFabric has no cost implications in and of itself, if you want to use the high availability features in an AppFabric cache, all cache hosts must be running Windows Server Enterprise Edition. There are more details on this here (para. 3), this also refers you to the installation guide (although having just read through the installation guide again I couldn’t see this restriction mentioned anywhere).

Download it here


Fabric, Fabric, AppFabric

What is it?

Windows Server AppFabric is application infrastructure for running and managing your services – infrastructure that you now don’t have to write. Windows Communication Foundation (WCF) provides a single programming model for creating services and communicating between them – it is the communications scaffolding around your service’s application logic. For long-running services and coordinated interactions across many services, AppFabric manages the lifetime and scaling of Windows Workflow Foundation (WF) workloads as well, since workflows in AppFabric are also services. But that’s just half the story.

The other half of the story is all about data caching. It’s fundamental to application design that you shouldn’t repeat a computation that always returns the same result; do it once, store it, and deliver the result repeatedly instead. This is true whether the result is a webpage, a query from your database, or a service call to an external component. The Windows Server AppFabric Cache stores .NET objects, scales seamlessly, and manages data location and redundancy by distributing the cache across a cluster of machines. The developer can simply put data in the cache and retrieve it when needed – AppFabric handles all the underlying complexity for you.


How does it look?

AppFabric does its job mostly in the background, invisible to the user. The visible face of AppFabric is the management and monitoring tools for your services that have been integrated into IIS Manager. These tools drive the UI management experience for service hosting. AppFabric services are integrated into the system management services such as perfmon and logging which can then be further integrated into a broader systems management infrastructure.


Workflow and WCF Code Services

AppFabric manages both WCF services and Workflow Services (which are also WCF Services). The difference lies in what’s inside the service. With WCF, it’s your code. With Workflow, you would typically have drawn your workflow using the Visual Studio Workflow Designer and a palette of re-usable workflow activities, including activities that allow you to make your workflow into a service and to call other services.

A workflow activity can also be thought of as a component and you can create new activities from existing ones – a composite activity. This is a very powerful model for composing applications out of components and very useful in the cloud journey as well as in applications today.

The Visual Studio WCF Workflow Service Application Template helps you get your workflow service up and running and see the results in AppFabric in just a few minutes. To start, create a new project using the template and set the Web Property on the project to use the local IIS Server. Build the project and run it. The built-in WCF test client will launch, allowing you to send data to your workflow and see the result. A similar template exists for WCF code based services, so you can immediately focus on your code based business logic and not have to write the WCF infrastructure or any of the related hosting and management capabilities that AppFabric now provides.


You can download AppFabric and learn more from the AppFabric page.



Refer :

How to configure AppFabric?

Install AppFabric using the link

See the below video for AppFabric configuration steps

Video details the AppFabric Configuration Steps



For additional learning use:-