Microsoft’s .NET Strategy: Introduction to WinFX

1. Microsoft’s .NET Strategy: Introduction to WinFX Robert Burke Developer and Platform Group Microsoft Ireland robburke@microsoft.com http://blogs.msdn.com/robburke

2. Agenda • Brief intro to .NET • Where we are today: 2005 technologies • WinFX Vision & Roadmap • Indigo • Avalon • Resources & Where to Learn More

3. VB C++ C# J# … Visual Studio.NET Common Language Specification ASP.NET WinForms Data and XML Framework Class Library Common Language Runtime Windows COM+ Services Intro to the .Net Framework

4. IncreasedReliability QualityEarly & Often Design forOperations Predictability& Visibility Developer Tester SolutionArchitect ProjectManager InfrastructureArchitect Visual Studio 2005: Team System

5. Improvements to WinForms 2, ASP.NET 2

6. Visual Studio 2005 Beta 2 Experience

7. TM Windows “Longhorn” Developer ArchitectureAs Announced at PDC 2003 Presentation Data Communication Base Operating System Services

8. Beta Beta Beta Developer Roadmap 2007 2006 2005

9. Indigo Overview

10. The Move to Distributed Applications

11. From Objects to Services Service Orientation (Today) Interface-based Dynamic Loading Runtime Metadata Components (1990s) Message-based Schema+Contract Binding via Policy Class-based Polymorphism Encapsulation Object Orientation (1980s)

12. The Four Tenets of SO Developers opt-in to consuming, exposing, and defining public-facing service façade. Boundaries are explicit Services and consumers are independently versioned, deployed, operated, and secured. Services are autonomous Data never includes behavior; Objects with data and behavior are a local phenomenon. Share schema & contract, not class Compatibility based on policy Capabilities and requirements represented by a unique public name; Used to establish service suitability.

13. Distributed Stacks Today ServicesInteroperableASP.NET Infrastructure ComponentsTransactionsCOM+ Infrastructure Objects Extensible CLR Infrastructure QueuingReliable MsgMSMQ Infrastructure • Each stack has different strengths, target scenarios • Customers want to mix and match, compose • Reliable services • Interoperable transactions

14. The Union of Today’s Stacks Message- Oriented Programming Attribute- Based Programming WS-* Protocols Composability Extensibility SOA Interop

15. Indigo Architecture

16. CLR Type Integration Behavior CLR Type Integration Behavior Error Handling Behavior TCP Transport Channel HTTP Transport Channel TCP Transport Channel UDP Transport Channel Queue Transport Channel HTTP Transport Channel UDP Transport Channel Throttling Behavior Transaction Behavior Instancing Behavior Instancing Behavior Custom Behavior Metadata Behavior Custom Behavior Custom Channel Security Channel Security Channel Custom Channel Full Duplex Channel Reliable Messaging Channel Reliable Messaging Channel Concurrency Behavior Cross-Proc Transport Channel Composability in Action Service Model Layer Messaging Layer Behaviors Channels

17. [TcpTransport] [CustomTransport] [ServiceContract(SecureChannel=true, SecurityMode ="Windows")] [ServiceSettings(InstanceMode=InstanceMode.PerCall)] class MyService { [CustomBehavior] [ServiceOperation(TransactionFlowAllowed = true)] void DoSomething(string argument) { // Do something transacted here } } Feature Overview Programming Model

18. Cross-Platform Interop ReliabilityWS-Reliable Messaging TransactionsWS-AtomicTransaction WS-Coordination SecurityWS-Security WS-Trust WS-Federation Metadata WSDL, WS-Policy, WS-Discovery Messaging SOAP, WS-Addressing, WS-Eventing XML XML, XSD, XPath Transports HTTP, TCP

19. Summary: The move to distributed applications

20. Avalon Overview

21. “Avalon” Integrated Presentation System Deliver Superior User Experiences Improve Development Productivity Increase Product Differentiation

22. Avalon Vision • 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

23. Avalon Application Model Document Model Graphics Model Tools and Languages Element Services Media Integration Layer Composition and Rendering DirectX .NET Framework Unified Approach to UI, Documents, and MediaIntegration: The Guiding Vision • Application Model • Composable component architecture • Layout engine • Two-way transformable data binding • Rich visual styling and theming • Browser hosting • Graphics Model • 2D & 3D Graphics • Imaging • Text • Video and audio • Animation • Document Model • Fixed, flow and adaptive layouts • Advanced typography • Container services • Rights management

25. Integrated Vector-based Graphics and Composition • Modern graphics capabilities • 2D and 3D graphics • Image effects and codec • Hardware accelerated sub-pixel ClearType • Video and audio • Revolutionizing the Graphics and Media pipeline • Across the display, audio, printing, and remoting sub-systems • Direct3D-based hardware acceleration throughout the rendering pipeline • Anticipates future hardware technologies • Resolution independence • Double floating point precision • Deeper color pipeline Enabling high-quality, cinematic experiences

27. Markup for Windows 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 <Button Width="100"> OK <Button.Background> LightBlue </Button.Background> </Button> Button b1 = new Button(); b1.Content = "OK"; b1.Background = new SolidColorBrush(Colors.LightBlue); b1.Width = 100; Dim b1 As New Button b1.Content = "OK" b1.Background = New _ SolidColorBrush(Colors.LightBlue) b1.Width = 100

30. Avalon 1.0 Target Scenarios • Avalon is the future of Windows presentation technology • Other technologies are often still better choices today • Recommended Avalon 1.0 usage • Web sites that want to push the limits of user experiences • Windows applications with complex data visualization scenarios • Windows Forms is still the best solution for mainstream rich client Windows applications • DirectX is still the platform for extremely intensive graphics (games, CAD applications) • ASP.NET is the reach solution for server-based platform-agnostic applications

31. WinFX Requirements & Distribution • System Requirements • Windows XP SP2, Windows Server 2003 or higher • Pentium-class 1GHz CPU (minimum) • At least 256MB RAM • DirectX 9 hardware accelerated graphics (preferred) • Distribution Strategy • Available via Windows Update • Working on pre-install arrangements w/ major OEMs (currently 60% shipping .NET Framework) • Included with Windows “Longhorn” (speaking of which…) • Fully Redistributable

32. Windows Forms Windows Forms Avalon WinFS Indigo ASP.NET ADO.NET Collaboration Document UI Media Object T/SQL XML Service Models Queuing Eventing Schemas Messaging Services Connectivity Services Routing Controls Interop Engine Desktop Window Manager Adaptive UI Engine Desktop Services People and Groups ObjectSpaces People Group Channels (Datagram, Reliable, Peer, …) Policy Engine Synchronization(WinFS, Win32..) Calendar Media Page/SiteComposition Presentation Object Manager Desktop Composition Engine Application Services DataSet Collaboration History Document … Channel Security Transport Channels (IPC, HTTP, TCP…) Data Model Media Services InfoAgent (PreferenceRules..) Message Encoder SQL XML Real-Time Activities Items Animation andComposition MediaProcessing Capture and Sourcing Designer Services Personalization and Profiling Services System Services Relationships FileSystem Services (MetaDataHandlers..) Communications Manager (Port) Transaction Framework Providers Signaling Hardware Rendering Software Rendering and Sinks Controls Membership and Security Services Extensions Federation CLR Base Class Libraries Network Class Library Memory Manager Code Execution Loader Security Serialization Application Deployment Engine (Click-Once) Network Services Demand Activation and Protocol Health Hosting Layer PNRP Native WiFi SIP TCP Listener UDP Listener IPC Listener Transactions Storage Identity & Security System Management Services (Event Logs, Tracing, Probes, Auto Update, Admin) GDI/GDI+ Window Manager Global Audio Engine Direct 3DGraphics Virtual Shadow Copy Service File Replication Service Virtual Disk Service Lightweight Transactions TransactionCoordinator Internet Connection Firewall Graphics drivers DDI Input Manager Audio Drivers DirectX Graphics Mini port Protocols Redirectors Distributed File System Filter Manager Cache Manager KernelTransactionManager LoggingService Filter Engine TCP, UDP IPV4, IPV6 IPSEC QOS HTTP Listener Transacted NTFS Universal Data Format FAT 16/32 Plug andPlay MemoryManager PowerManager ConfigManager Process Manager SecurityReference Monitor LPCFacility IO Manager Device Drivers Kernel Mode 802.3 802.11 .. Kernel SCSI/FC Hardware Abstraction Layer How does Longhorn fit into this? Presentation Data Communication Avalon WinFS Indigo Base Operating System Services

33. Visual Studio 2005 Beta 2 Experience

34. For More Information • Visual Studio 2005 Beta 2 Experience • http://www.microsoft.com/emea/msdn/betaexperience • WinFX SDK • http://winfx.msdn.microsoft.com/library • Channel 9 • http://channel9.msdn.com/ • Longhorn Developer Center • http://www.msdn.microsoft.com/longhorn • Microsoft Ireland MSDN weblogs • http://blogs.msdn.com/robburke • http://blogs.msdn.com/claredil • http://blogs.msdn.com/billobr