Windows Communication Foundation

1
Windows Communication Foundation
Client
Service
Eric Nelson Eric.Nelson_at_microsoft.com
Application Architect Microsoft
Ltd http//blogs.msdn.com/ericnel
2
Challenges

• How do I ensure reliable connectivity?
• How do I support rich authentication types?
• How do I ensure interoperability with other
  platforms?
• How do I make my distributed applications less
  fragile?
• How do I make them service-oriented?
• Which programming model should I use?

3
Where Are We Today?
J2EE
Microsoft
JAX-RPC
ASMX / WSE
RMI
Remoting
CORBA
DCOM
EJB
Enterprise Services
JMS
System.Messaging
Sockets
Sockets
4
Today writing plumbing code
Using Visual Studio .NET 2003 and WSE
5
Windows Communication Foundation
6
Unified Programming Model
.NET Remoting
ASMX
Interop with other platforms
Extensibility Location transparency
Attribute- Based Programming
Message- Oriented Programming
WS- Protocol Support
Enterprise Services
System.Messaging
WSE
7

• WCF extends the .NET Framework
• Services are built in Visual Studio 2005 using
  any .NET programming language
• Intelligent code editing
• Service templates
• Debugging

8
Investment ProtectionLeveraging Existing
Microsoft Investments

• Side-by-side co-existence with existing
  distributed technologies
• Seamless communication with applications built on
  existing technologies
• Smooth upgrade of existing code to WCF

ASMX
ASMX
9
ASMX to WCF
using System.Web.Services      public class
AccountingOperation     public string
AccountName     public long Amount       
  public class Accounting    
WebMethod(TransactionOptionTransactionOption.Req
uiresNew)     public int AddEntry(AccountingOpera
tion debit,                         AccountingOper
ation credit)             // Add entry to
internal accounting book         // return
id.    
//
using System.ServiceModel
ServiceContract(FormatModeContractFormatMode.Xml
Serializer)
//
OperationContract OperationBehavior(AutoEnlistT
ransactiontrue)
10
Tomorrow writing logic
Using Visual Studio 2005 and Indigo
11
Windows Workflow Foundation
12
Windows Workflow Foundation
Windows Workflow Foundation is the programming
model, engine and tools for quickly building
workflow enabled applications on Windows.

• Single workflow technology for Windows
• Available to all customers of Windows
• Available for use across a broad range of
  scenarios
• Redefining workflow
• Extensible framework API to build workflow
  centric products
• One technology for human and system workflow
• Take workflow mainstream
• Incremental learning for mainstream .NET
  developer
• Fundamental part of the Office 12
• Strong workflow partner solution ecosystem

13
Workflow and BizTalk Server
BizTalk Server

• Premium BPM server
• Application to application and B2B integration
• Connects multiple services built with WCF
• Adapters to multiple products like SAP and
  MQSeries
• Business activity monitoring
• Vertical solutions and industry accelerators
• Message transformation services
• Enterprise single sign-on
• End-to-end health and activity tracking
• And more

Business Activity Monitor And Admin Tools
Accelerators
Design Tools
Workflow
Orchestration
Messaging
Transformation
Adapters

• Workflow framework
• Exposed via WinFX
• Broad set of scenarios
• Used to build solutions
• Enables manageability
• and scale-out in solutions
• Use for building workflow into apps or
  workflow-enabled servers

Visual Studio Designer
WinFX
Windows Workflow Foundation
14
What is a workflow?
A set of activities that coordinate people and /
or software...
EscalateToManager
CheckInventory
Example activities.
15
Workflow Scenario Spectrum

• Participants people, roles
• Flow style flexible, dynamic
• Data unstructured, documents

• Participants apps, services
• Flow style prescriptive, protocols
• Data structured, transactional

16
Why Workflow Technology?
17
Why Workflow Technology?
Real World Examples
Workflow Value-Add
Long Running and Stateful Workflows run for up to
30 days and maintain state throughout
Orders are confirmed in 48 hours and shipped
within 30 days.
Most suppliers confirm our orders but some
forget and we need to followup.
Flexible Control Flow Flexibility for people to
override or skip steps in the workflow
Transparency Rendering a visualization of next
steps based on defined control flow
What are the next steps in handling this order?
18
Building a Workflow
19
Take the Next Step

• Start programming with Visual Studio 2005
• Download and evaluate WinFX
• Lunch 1230 til 100pm
• This afternoon
• WPF http//windowsworkflow.net
• WCF and WWF http//windowscommunication.net
• Call To Action (links, early adopter
  opportunities)

20
(No Transcript)