I've looked at building a .NET NAnt BuildServer to assist in Continuous Integration...however, I've stumbled upon Draco.NET which may do me one better.

"Draco.NET is a Windows service application designed to facilitate continuous integration. Draco.NET monitors your source code repository, automatically rebuilds your project when changes are detected and then emails you the build result along with a list of changes since the last build."

W3C Home Page Table-less Layout: HOWTO. [ via Zeldman ]
The W3C explains how they do a three column, tableless layout on their front page. [More Like This WebLog]

This is pretty slick...I've got a few sites that could benefit from a tableless layout...

The Five Biggest Myths About Web Services

Myth No. 1: Web services is brand new.
Myth No. 2: Web services has so many shortcomings, such as security, that it will prove to be a disruptive element in an organization's IT efforts.
Myth No. 3: Interoperability will never happen. We've all got to have the same operating system to make Web services work best.
Myth No. 4: Getting Web services means getting rid of all your current software and developing new programming languages to handle the Tower of Babel you're going to face.
Myth No. 5: Web services is the endgame--the goal we're aiming toward.

Great list of the 5 biggest myths about Web Services...up at PatrickWeb's list of the 5 Next Big Things.

ILLINK Microsoft (R) .NET Framework IL Linker

The ILLINK utility is intended for linking multiple managed modules or assemblies into a single module or assembly...  [Adrian Bateman (VisionTech)]

Nice little tool from Serge Lidin.  It works by running ILDASM, doing some string grinding, and then running ILDASM on the result.  The program is about 500 lines of raw C++ - it would be interesting to rewrite it in C# or VB.NET. Even cooler - write it using Jim Miller's PEWriter libraries and dispense with ILASM / ILDASM altogether...
[Managed Space]

Hm!  This is clever...

Great article on on MSDNMag by Yasser Shahoud on building your Web Services around Message Structures

SUMMARY: Web Services are all about exchanging data in the form of XML messages. If you were about to design a database schema, you probably wouldn't let your tool do it for you. You'd hand-tool it yourself to ensure maximum efficiency. In this article, the author maintains that designing a Web Service should be no different. You should know what kind of data will be returned by Web Service requests and use the structure of that data to design the most efficient message format. Here you'll learn how to make that determination and how to build your Web Service around the message structure.