Windows Server Longhorn What s New For Developers Gianpaolo

Windows Server “Longhorn”: What's New For Developers Gianpaolo Carraro DAT 202 Windows Server Evangelism Microsoft Corporation 1

Quiz: Are you a Windows Server “Longhorn” Developer? 1. Do youyou everfunctionalities 4. Have access had a system 3. Do 4 Questions frequently revisit 2. you need to authenticate or found in existing/legacy systems andthat administrator coming to you saying do your code= 1 point + Raisein business authorize users coming from outside due changes your hand Yes them to stopped working and you need your application “talk” secure, reliable to processes 0 point events you need to your corporate boundaries? No idea why? protocols)? = or new Web Services (WS-* has no react on ? Bonus question: Was you answer: “Strange…It works fine on my machine ? !” 2

Quiz Results 3 or 4 Points You are a Longhornoholic Windows Server More seriously, many of you, have answered Yes: “Longhorn” was made for you, install the bits right • Not incidental the end of all your pains away and enjoy • New class of application 1 or 2 Points • New requirements for application platform You will still highly benefit from Windows Server “Longhorn”, make sure you dive deeper in the various areas of interest to rip maximum benefit 0 Point What Windows Server “Longhorn” is all about Are you sure you are a developer? 3

Windows Application Platform History Programmable Web Era -. net - Platform for Web Services - Windows Server 2003 Web Era: Next Step: Connected Systems Era -Platform for Web - 5 Pillars of-Windows DNA Connected Systems - Windows Server applications Platform for Connected Systems -3 tier “Longhorn”: -Windows NT 1996 2000 2005 4

Connected Systems Scenario: The Employee Relocation Issue work Visas Connected Principles. Systems Secure, reliable messaging Service-oriented + Government Pervasive workflow Legacy integration Multiple identities, Identity Federated web single TODAY… Implementing all of this is possible sign on Federated data BUT Corporate HR Mortgage Broker Long running transactions + User-centric Many short lived “ad hoc” Offer online mortgages workflow Operationally aware HR systems Credit checks Employee Needs to arrange move, travel, house hunting trip Apply for a work visa / mortgage Model-based Rich visualization + Entity Trustworthy aggregation + End to end health monitoring+ Service activation / hosting + ARCSYM … 5

5 Pillars of Connected Systems Censored by “PDC Police” ASP. NET 2. 0 Atlas Office 12 Windows Vista Infocard AD WCF This session LINQ Win. FS SQL 2005 6

Legacy System Interop Marc Mercuri Windows Server Evangelism 7

Scenario #1: Legacy System Interop Consume WS-* Services from Legacy Applications Employee Woodgrove Expose Legacy COM+ Applications as WS-* Services Contoso, Inc. IIS 7 WCF WS-* Service Purchasing COM+ Lotus Notes COM+ Component as WCF Service COM Lotus Script Using COM interface To Third Party WCF Service 8

What is the big deal here? Exposing Legacy Code as WS-* Services Allowing Legacy Code to tap into WS-* Services IIS 7: Modularization and Extensibility Additional Information: COM 305 COM 209 9

Identity and access at PDC Green, Yellow, Red… badges; they represent claims Driver license (or other picture ID) to get the badge (need birth certificate or passport to get a driver license) Federated model Cannot get into breakout room with driver license Claim based 3 rd Party. Multiple issuing authorities Security staff check badges Entry allowed based on “color sheet” Policies Badge issued by Event company (not Microsoft) Role lists were provided by Microsoft 10

Ethernet Cable “Neighbor. Net” Open door to allow cable to come in Channel 9 guys Federated Identity and Claim based access control In Italy at Mamma’s Remote Desktop into getting internet. Mc. Murtry Craig access demo server. from upstairs neighbor Windows Server Evangelism Demo server on my manager’s desk (he wanted to “see” the demo so here it is…) 11

Scenario #2 Federated Identity and Claim based access control 12

What is the big deal here? Federated Identity Claim Based Authorization Chain of Trust Additional Information: COM 214 COM 321 13

Workflow Pillar Demo Tomorrow!!! 14

Manageability Eventing and organizations Augmented relationship among Tracing: = “Crimson” Instrumentation: Augmented dependencies = WMI Performance Service Level Agreements Counters Management Scripting: = WS-Management Must understand control Monad of what is going on in the systems Task Scheduler NEXT STEP: secure manageable app 15

Why is Manageability Important? Easier to troubleshoot and maintain (you know what happens) Less time maintaining == more time building apps Less maintenance cost == more $ on new apps Either low cost or more value for the $ Improve system compliance with business IT policies Better communication with “other side of IT” Knowledge Lifecycle 16

Health Models and Instrumentation Gianpaolo Carraro Windows Server Evangelism 17

Scenario #3: Health Models and Instrumentation WS-Management Employee Simple App Events Logged via “Crimson” Application Log Task Scheduler Executes Script (WS-Management) Task Execution Task Scheduler Triggered By Event 18

What is the big deal here? Health Modeling Monitoring – Diagnosing – Healing Cycle Additional Information: FUN 311 COM 308 19

Fundamentals Windows Internals Transactional File System Transactional registry User Mode Driver Framework, Power management Hybrid Sleep Security Crypto Next Generation Service Hardening Fundamentals 20

Transactional File System A very simple demo Gianpaolo Carraro Windows Server Evangelism 21

What is the big deal here? Simple way to add data reliability to your application Can transact updates to file system and registry Transactions can be coordinated with databases and with other machines File system transactions work remotely Additional Information: DAT 406 FUN 320 22

And few more pointers: Service hardening, New Crypto and UAP FUN 210 Computer Cluster Solution DAT 301 Windows Internals FUN 417 More Reliable Application FUN 308 23

So… what’s new for developers? Application Platform Management Manageability Fundamentals Platform for Connected Eventing Internals Windows and Systems Tracing: “Crimson” File Transactional Application Server: System Instrumentation: Registry Transactional CLR 2. 0 WMI Mode Driver Framework, User Win. FX Performance Counters Sleep Power management Hybrid Scripting: Web Server: Security WS-Management IIS 7 Next Generation Crypto Monad Hardening Service AD Task Scheduler MSMQ Fundamentals 24

But wait… we’re not done yet… let’s finish with another demo… 25

Craig Mc. Murtry Windows Server Evangelism 26

Claims-based Identity … breaks our identities out of their shells … Upn=My. DomainMy. User. Name Role=My. Role Thumprint=t 684 er. M%2@. … and gets them moving, as claims, across the wire 27

So, can we now solve … The #1 identity problem on the ‘Net? Who are our kids talking to online? 28

29

30

31

Final Words… A lot of developer innovation in “Longhorn” timeframe This was “just a taste” Go deeper in the areas of interest in the next few days Code of demos will be available on blogs or Comm. Net 32

Community Resources Blogs http: //brettblog. com http: //blogs. msdn. com/craigmcmurtry http: //blogs. msdn. com/daiken/ http: //blog. advisor. com/blog/garydev. nsf http: //blogs. msdn. com/gianpaolo http: //blogs. msdn. com/jamescon http: //www. marcmercuri. com http: //blogs. msdn. com/vbertocci Early Adoption Programs ISV Programs Enterprise Programs Contact your local Microsoft Developer and Platform Evangelism team or gianpc@microsoft. com 33

© 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 34