[CLIL01] The Windows "Longhorn" SDK: Powering the Creation of Next Generation Applications

Today I got an email from a coworker about the meaning of WinFX: “Is WinFX a new marketing name for .NET”?

No, it isn’t. WinFX is the managed API, the SDK of Longhorn. Steven Goulet, the speaker of this session, said: Everything in Longhorn is in the SDK. Or: What’s not on the SDK, is not in the OS.

Steven has done some comparison between the .NET framework 1.0 and WinFX:

	.NET 1.0	WinFX (PDC build)
Assemblies	39	>100 *
Namespaces	121	438
Types	3889	13595
Implemented members	32523	93217

^*Sorry, I cannot read my own hand-writing

• High Level for Productivity
• Low Level API for Power and Flexibility

Good news about the documentation:

The documentation is currently about 200.000 pages (Oxford English Dictionary has about 22.000)

Longhorn SDK Vegas: Next Generation Longhorn SDK content delivery and publishing/viewing technology.

There will be no Platform SDK for Longhorn, only WinFX.

The documentation is living, i.e. it will be updated regularly via Internet, the help pages will have kind of a discussion forum attached, so build-in feedback.