Busy days and Longhorn connectivity

Windows Vista Comments

I haven't blogged since a few days. That's because stayed another two days after the PDC in Los Angeles, but I didn't have any web access. By the way, these two days in L.A. were a mess, since the public transportation is on strike since three weeks. Thus I haven't seen that much of the City of Angels Sad

Anyway, in the meantime it's Tuesday, and I have installed Longhorn on two boxes, one at work and one at home. Unfortunately, Longhorn doesn't include the proper network drivers. Though I could use the Windows XP drivers for my machine at  work (which board is a ASUS P4C800 Deluxe with an Intel 875P chipset), I wasn't able to get my home machine online (ASUS A7N8X with nVidia nForce2), not even with the Windows XP drivers... does anyone else have such a set-up? I'd like to use my home PC as my primary "Longhorn experience center."

The Return of the Console

PDC '03, MSBuild Comments

I've never stopped using the console since the good old DOS. In fact, each developer at our company is using the console, i.e. 4NT. Our development environment depends heavily on the console, the complete build and deployment process is realized with batch files.

What really suprised me at the PDC is Microsoft's homage to the console.

  1. In more of half of the sessions I attended you were able to see the speaker using the console. Probably that's mainly a plug for the new MSBuild tool. But anyway, they're using it.
  2. With the next version of the CLR you're able to colorize the output to the console.

However, it's sad to see people who don't know anything about the console...

[TLS321] Visual C# "Whidbey": IDE Enhancement for the C# Developer

Whidbey, PDC '03 Comments
  • Nice new features in the IDE:
  • Expansion, configurable via XML schema (e.g. automatic getter and setter for properties)
  • Code formatting (customizable)
  • Filter completion list (e.g. the list in catch( contains exception classes only)
  • Browse components (generates read-only source files, e.g. for System.String)
  • Find all references
  • Refactoring (e.g. Rename, Extract method, etc)
  • Watch window in debugger will use .ToString() method

BTW, about 64% of the PDC attendees state their preferred .NET language is C#.

P.S.: Eric Rudder said in today's keynote, that currently 27 languages are supported in .NET...

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

PDC '03 Comments

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.