WCF



Overview


Building a distributed system is a very common task for many programmers. However, doing so involves
confronting numerous design challenges. In this chapter, you will review two key aspects of many distributed
systems (interfaces and XML web services), followed by an overview of Service-Oriented Architectures
(SOAs). Also, you will survey several core distributed APIs found within the Windows OS.
With this historical background in place, the remainder of this chapter will introduce you to the Windows
Communication Foundation (WCF) API. Here you will learn about the problems WCF attempts to solve,
study the ABC’s (addresses, bindings, and contracts) of building a WCF application, and explore some
common WCF development tools.
The information presented here will function as the backbone for the remainder of the class.

A Working Definition of Windows Communication Foundation (WCF)

To begin your examination of WCF, you will start with a review of common distributed programming
practices and previously distributed APIs. This is important, given that WCF leverages many of the
distributed concepts / APIs you may have used in the past.

WCF is a .NET 3.0 (and higher) API that allows you to build distributed systems. WCF is unique in that you
can select from many types of bindings. This fact alone makes WCF a very flexible framework. A single WCF
service could be exposed via an HTTP binding for outwardly facing callers or via a TCP binding for in-house
callers. The underlying plumbing details can be relegated to *.config files, which make it very simple to change
bindings and other details on the fly.

WCF makes extensive use of interface-based programming techniques. When you define a WCF service, you
typically begin by defining the interfaces that model the functionality callers can expect to find. These .NET
interfaces could be used by the runtime to generate WSDL definitions based on your choice of bindings.

In addition, WCF makes heavy use of .NET attributes to qualify how the runtime should handle client /
service interactions. Similar to the .NET remoting layer / XML web services, WCF attributes are used to
control data formatting, binding operations, and more. Recall that attributes are essentially code annotations.
Attributes are useless unless another piece of software reflects over them.  In this case, the ‘other piece of
software’ could be the WCF runtime as well as WCF development tools.

WCF is heavily influenced by XML web services and Service-Oriented Architectures (SOAs) in general. Like
an XML web service, WCF services make use of contracts and explicit boundaries and support the use of
various WS-* specifications.

However, a WCF service does not have to use web-service-centric bindings. If you wish, you can opt for P2P
bindings, named pipes, TCP bindings, and so on. The underlying binding is decoupled from the service itself. 
Therefore, changing bindings on the fly is very straightforward.

In a nutshell, as of .NET 3.0 (and higher), WCF is the preferred way to build new distributed systems. The
original distributed .NET APIs (System.Runtime.Remoting, System.Web.Services, and so forth) are still
supported. Furthermore, Visual Studio still has templates for ‘traditional’ ASP.NET web service project
workspaces.

It is also possible to migrate existing XML web services / remoting applications into the WCF programming
model. Doing so, however, may offer little benefit. In fact, it could entail a good amount of work.

This course does not cover migrating existing distributed systems into the WCF programming model. The
class assumes you intend to build new WCF services, hosts, and clients. However, Appendix A illustrates
how to interact with legacy COM+ components. You can read Appendix A if time / interest permits.

The .NET Framework SDK documentation provides details of migrating existing systems. If you are
interested in migrating from .NET remoting to WCF, look up the article ‘From .NET Remoting to the
Windows Communication Foundation (WCF)’. If you are interested in migrating from ASP.NET web
services to WCF, look up the article ‘Migrating ASP.NET Web Services to WCF’.

Finally, be aware that this class will focus on the core aspects of the programming model, which will be
commonplace to all of your WCF projects. Consult the .NET Framework SDK documentation for WCF
topics not addressed in this course. The WCF section of the SDK documentation provides a number of
excellent code examples, white papers, and tutorials.  Simply look up the Windows Communication
Foundation selection of the help system and dive in.
WCF Tutorial

Comments

Post a Comment

Popular posts from this blog

SharePoint: Group By on more than 2 columns in a view (SP 2010)

Image
An expanded version of this article, along with many other customization examples and how-tos can be found in my book,  SharePoint 2007 and 2010 Customization for the Site Owner . This is an update of an  article written for SharePoint 2007 . Many of the steps are the same in both 2007 and 2010, but both the SharePoint Designer steps and the default web part used for views have changed. Group By on more than 2 columns in a view In my SharePoint classes I have often been of asked how to group on more than two levels in a view. I have always given the quick answer of "use SharePoint Designer"!  But, some of you have asked "How?". You may be sorry you asked… but here goes…  Goals:  Create a view with nested groups deeper than just 2 levels Put the counts and totals at the bottom of each section. Do the above with no custom web parts, custom XSLT or anything that has to be deployed to the server. Sample:       Secrets and Tricks needed:  It can't be done &
Read more

Configure Form Based Authentication (FBA) in SharePoint 2010

Image
Steps to Configure FBA in SharePoint 2010  Below are the steps required to configure FBA in SharePoint 2010. I will be using MS SQL database as membership store for users.   A) Setting up ASP.NET Forms Authentication User and Role Data Source  1. Create Database  2. Configure Membership and Role Provider  3. Create User B) Create Web Application and Site Collections C) Configure Web.Config file  1. Configuring FBA web application web.config file 2. Configuring Central Administration web application web.config file 3. Configuring Security Token Service web.config file D) Adding User Policy to the FBA Web Application E) Verification Steps  A) Setting up ASP.NET Forms Authentication User and Role Data Source  This section explains creation of database which is used to store user's information such as credentials and roles which is used for Form Authentication. This section also explains the configuration of Membership and Role providers in the web.
Read more

SharePoint 2010 Windows PowerShell Interview Questions

Q. What is Windows Powershell ? Ans.  Windows PowerShell is a new Windows command-line shell designed especially for system administrators. In the SharePoint administration context, Windows PowerShell is another administration tool that supersedes the existing Stsadm.exe. Q. How is Windows Powershell different from Stsadm ? Ans.  Unlike stsadm, which accept and return text, Windows PowerShell is built on the Microsoft .NET Framework and accepts and returns .NET Framework objects. In addition to that it also gives you access to the file system on the computer so that you can access registry,digital signature certificate etc.. Q. What are cmdlet's? Ans.  Windows PowerShell introduces the concept of a cmdlet which are simple build in commands, written in a .net language like C# or VB. Q. Can you Create PowerShell scripts for deploying components in SharePoint ? Ans . If you are creating a webpart with VS 2010 then you can deploy it using ctrl + f5. However, to activate the
Read more