Jeremy Boyd Intergen

1
WinFXManaged APIs for Windows

• Jeremy Boyd - Intergen
• MSDN Regional Director
• jeremyb_at_intergen.co.nz

2
Windows Platform
3
Agenda

• Quick tour through WinFX
• Windows Presentation Foundation
• Windows Workflow Foundation
• Windows Communication Foundation

4
Windows Presentation Foundation

• Enabling the User Experience for Developers

5
Presentation Challenges
How do I improve productivity and usability?
How can software exploit available hardware and
form factors?
How do I differentiate my software from my
competition?
How can my software reach the broadest possible
audience?
How can developers and designers collaborate?
6
Windows Presentation Foundation

• Unified approach to UI, Documents, and Media
• Integration as part of development and experience
• Integrated, vector-based composition engine
• Utilizing the power of the PC throughout the
  graphics stack
• Declarative programming
• Bringing designers directly into application
  development
• Ease of deployment
• Allowing administrators to deploy and manage
  applications securely

7
Microsoft Presentation Technologies
Availability
8
XAML

• Extensible Application Markup Language
• Build applications in simple declarative
  statements
• Can be used for any CLR object hierarchy
• Code and content are separate
• Streamline collaboration between designers and
  developers
• Easy for tools to consume and generate

9
XAML in context of WPF

• WPF Rich Control Library
• Border, BulletDecorator , Button, Canvas ,
  CheckBox , ComboBox , ContextMenu , Control ,
  DockPanel , DocumentViewer, Expander ,
  FlowDocumentPageViewer , FlowDocumentReader ,
  FlowDocumentScrollViewer , Frame , Grid ,
  GridSplitter , GridView , GroupBox , Image ,
  Label , ListView , ListBox , Menu , Panel ,
  PasswordBox , Popup , Tooltip, etc etc.
• Panels
• Styles and Resources
• Animations, Triggers, Storyboards, Timelines
• Bindings

10
Windows Presentation Foundation
11
Windows Workflow Foundation

• Enabling Workflow in Applications

12
What is a Workflow?

• A set of activities
• that co-ordinate people or
• and/or software
• in to some kind of process or flow
• Examples Flowchart, State Diagram

13
Software Challenges

• Long Running
• Orders are shipped over 30 days
• Flexible Flow Control
• This must be approved NOW!
• Transparency into running state
• What's going on with this process??
• Transactional
• Its all, or nothing..

14
Traditional Implementation
15
Windows Workflow Implementation
16
Workflow Solutions with WF

• Supports long running transactions
• Allows flexible flow control
• Allows monitoring
• Allows transactional boundaries
• Allows unification of business analyst, developer
  and end user view

17
Opportunities with Workflow

• Business Applications LOB / B2B
• IT Management
• Information Worker Process

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

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

18
Workflow Basics

• Workflows are sets of activities
• Workflows are hosted in a process
• Workflows are executed in the WF runtime
• Workflows can be persisted

19
Windows Workflow Foundation
Base Activity Library
My Workflow built using Visual Designer
Windows Workflow Runtime
Workflow Services
Windows Workflow Foundation
Hosting Process
20
Workflow Basics
Workflow is a Class
Workflow can also be defined in markup (XOML)
21
Windows Workflow Foundation
22
Windows Communication Foundation

• The unified framework for building
  Service-Oriented
• applications.

23
Service-Oriented Tenets
Boundaries are Explicit
Service and Consumer are separated by an explicit
façade.
Services and consumers are independently
versioned, deployed and operated.
Services are autonomous
Data never includes behavior
Share schema contract, not class
Requirements of service declared independent of
contract e.g. Security
Compatibility based on policy
24
Endpoints
Endpoint
Endpoint
Endpoint
Endpoint
Client
Service
25
Address, Binding, Contract
A
B
C
Client
Service
Address Where?
Contract What?
Binding How?
26
Creating and Consuming
A
B
C
Client
Service
27
Contract and Service Definition
ServiceContract public interface IHello
OperationContract string Hello(string name)
OperationContract MyMessageOut
DoIt(MyMessageIn m)
public class HelloService IHello public
string Hello(string name) return Hello,
name public MyMessageOut
DoIt(MyMessageIn m) return new
MyMessageOut()
28
Service Configuration
App.Config lt?xml version"1.0" encoding"utf-8"
?gt ltconfigurationgt ltsystem.serviceModelgt
ltservicesgt ltservice typeHelloService"
ltendpoint addresshttp//localhost/Hel
loService"
bindingbasicHttpBinding"
contract"IHello" /gt lt/servicegt
lt/servicesgt lt/system.serviceModelgt lt/configurat
iongt
29
Standard / Specification Support
30
Windows Communication Foundation
31
Summary

• Windows Presentation Foundation gives us the
  opportunity to build a great user experience
• Windows Workflow Foundation gives us the
  opportunity to model effective business process
• Windows Communication Foundation gives us the
  opportunity to build service-oriented systems
• WinFX is beta, but with a go-live licence get
  it now! ?

32
Binding Features

• Encoding
• Transport
• Security
• Reliable Messaging
• Transactions

33
Which Binding Do I Use?
Interop?
Local?
No
Yes
NetNamedPipeBinding
No
Yes
What Level?
Need Queues?
Basic
Yes
BasicHttpBinding
NetMsmqBinding
No
WS-
Duplex?
Peer to Peer?
No
Yes
WsHttpBinding
NetPeerTcpBinding
No
Yes
WsDualHttpBinding
NetTcpBinding