Windows Server “Longhorn”:

What's New For Developers

Gianpaolo Carraro
DAT 202
Windows Server Evangelism
Microsoft Corporation
 Quiz:
Are you a Windows Server “Longhorn”
Developer?

1.
4.Do
Have
youyouaccess
everfunctionalities
had a system
3.
2. Do
4 you need to frequently
Questions authenticate
found
administrator
in existing/legacy
coming tosystems
you saying
revisit
or authorize
Yes your
= 1 code
users
point due
+ coming
to changes
Raise from
your hand
and
thatdo
your
youapplication
need themstopped
to “talk”
in
outside
business
No = your
0 processes
corporateor new
point
secure,
workingreliable
and hasWeb
no Services
idea why? (WS-*
events
boundaries?
you need to react on ?
protocols)?

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

3
 Windows Application Platform History

Programmable Web Era

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

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

ASP.NET 2.0 Infocard LINQ

Atlas WCF WinFS
AD

Office 12 This session SQL2005

Windows Vista 6
Legacy System Interop

Marc Mercuri
Windows Server Evangelism

7
 Scenario #1:
Legacy System Interop
Contoso, Inc.

Consume IIS 7
WCF WS-* Service
WS-* Services Purchasing
COM+
from Legacy
Employee
Applications Lotus
Notes
Woodgrove COM+ Component
as WCF Service
Expose Legacy
COM+ COM

Applications Lotus Script Using COM interface

as WS-* Services 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

IIS7: Modularization and Extensibility

Additional
Information:
COM305
COM209

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

10
Ethernet Cable Open door to allow
“NeighborNet” cable to come in Channel9 guys

Federated Identity and

Claim based access control

In Italy at Remote Desktop Demo server on my

Craig McMurtry
Mamma’s into demo server. manager’s desk
getting internet (he wanted to “see” the dem
access
Windows Server Evangelism so here it is…)
from upstairs
neighbor
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:
COM214
COM321

13
Workflow Pillar Demo

Tomorrow!!!

14
Manageability

Eventing
Augmented relationship and organizations
among Tracing:
= “Crimson”
AugmentedInstrumentation:
dependencies
= WMI
Management Performance
Service Level Agreements
Counters
=
Scripting:
Must understand and control
of what is going on WS-Management
in the systems
Monad
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
Task Scheduler
Simple App Executes Script
(WS-Management
Events
Logged via
“Crimson”

Task Scheduler
Task Execution
Application Log Triggered
By Event
18
What is the big deal here?
Health Modeling

Monitoring – Diagnosing – Healing

Cycle

Additional
Information:
FUN311
COM308

19
Fundamentals

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:
DAT406
FUN320

22
And few more pointers:

Service hardening, New Crypto and FUN210

UAP DAT301

Computer Cluster Solution

FUN417

Windows Internals FUN308

More Reliable Application

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

Fundamentals

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

25
Craig McMurtry
Windows Server Evangelism

26
Claims-based Identity …
breaks our identities out of their she
…
Upn=MyDomain\MyUser Role=MyRole Thumprint=t684erM
Name %2@.

… and gets them moving, as claims, across 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

CommNet

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

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