1. Introduction to.NET FX 3.0 (+ sneak preview of.NET FX 3.5) Martin Parry Developer & Platform Group Microsoft Ltd Martin.Parry@microsoft.com http://www.martinparry.com Mike Taulty Developer & Platform Group Microsoft Ltd Mike.Taulty@microsoft.com http://www.mtaulty.com

2. Intro -.NET Framework v3.0 Shipped last year CardSpace, WCF, WPF, WF Supported on: - Windows XP SP2 Windows Server 2003 Windows Vista Uses CLR v2.0, VS 2005, no language changes

3. Intro -.NET Framework v3.5 Will ship with Visual Studio 2008 Currently available in Beta 1 Enhancements to some v3.0 features, plus new bits Still uses CLR v2.0 Visual Studio 2008 Some language additions

4. Agenda 9:45 – 11:00Martin Parry WCF and Windows CardSpace 11:00 – 11:15Break 11:15 – 12:30Mike Taulty WPF and WF 12:30Close

5. Windows CardSpace & Windows Communication Foundation (3.0 and a bit of 3.5) Martin Parry Developer & Platform Group Microsoft Ltd Martin.Parry@microsoft.com http://www.martinparry.com

6. Identity - Problems Passwords Too easy to crack, or too hard to remember I want multiple identities Because I don’t trust all recipients the same Results in identity silos on the web Banks etc. would like sign-on to be much more complex Human beings are the limiting factor Nobody trusts a single organization...

7. Identity – What’s the problem?

9. Identity - Solutions Must work cross-platform Must allow me several identities Must put me in control of my identities Must not put a single org. in charge Must allow recipients to define arbitrarily complex sign-on data...and protect the user from that complexity

10. What have we got?

11. The Identity MetaSystem Policy 2. “I would like a SAML 1.1 token, containing First Name, Surname, issued by *any*” 3. UI filters cards that can satisfy policy 4. User picks a card 5. Token is requested 1.Access resource 6. Token is created 7. Token is presented Relying Party Identity Provider

12. Types of Information Card Personal Card Refers to self-issued security token Securely stored on user’s PC Fixed set of claims available Managed Card Refers to Identity Provider that can issue tokens User’s PC stores only the IP details Claims are extensible

13. Windows CardSpace

14. What’s in the HTML? Click here to sign in <param name="requiredClaims" value="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress http://schemas.xmlsoap.org/ws/2005/05/identity/claims/privateperso nalidentifier" />

15. Communications Basic, Open Comms ASMX Ent Services Secure, Transactional WSE Secure, Open Comms Sys.Messaging MSMQ, Txns, Queuing Fast, Secure, Binary Remoting

16. Distributed Applications Services pass messages described by a contract Service may provide metadata, describing: - The contract The policy applied to communication “Client” Message “Service” Metadata Message (SOAP) Headers: Addressing, Security, etc. Body: Payload

17. What do I send? Where do I send it? How should I send it? Contract Address Binding Mechanics of Communication “Service” “Client” Transport? Encoding? Security?

18. Mechanics of Communication “Service” “Client” Endpoint Contract Binding Address Endpoint Contract Binding Address Endpoint Contract Binding Address

19. Basic WCF

20. Client WCF – sketched architecture Binding (ordered list of channel types & config) Binding (ordered list of channel types & config) channel type N channel type 2 channel type 1 config Your code Service Your code Metadata objects XML formatting channel Transport Channel (HTTP, TCP, MSMQ, Pipes, Peer) channel decoding encoding behaviours

21. Instancing, Concurrency, Sessions Service classes can be instantiated: - Singleton, Per-Call, Per-Session, Shareable Service code can be either: - Single threaded, Re-entrant or Multi-threaded Client Service Singleton Message B Message C Message A

22. Instancing, Concurrency, Sessions Service classes can be instantiated: - Singleton, Per-Call, Per-Session, Shareable Service code can be either: - Single threaded, Re-entrant or Multi-threaded Client Service Single Call Message B Message C Message A

23. Instancing, Concurrency, Sessions Service classes can be instantiated: - Singleton, Per-Call, Per-Session, Shareable Service code can be either: - Single threaded, Re-entrant or Multi-threaded Client Service Per Session Message B Message A session Per Session Message C

24. More WCF

25. Summary CardSpace Solving the problems associated with identity It’s the Identity Selector for Windows Part of cross-platform, open, identity metasystem Windows Communication Foundation Unified, highly extensible messaging API FX3.5 adds non-SOAP messaging

26. © 2007 Microsoft Ltd. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.