You have to stand on one foot, wait for 48 hours and wave a dead chicken over your monitor, but assuming you have the foot and the dead chicken, it don't cost nothin' to download the latest beta of Monad. Enjoy.

If I were doing AJAX work in ASP.NET, Ajax.NET is the kind of thing I'd want to use.

This is fabulous! Let me give you a taste:

“We use words like L2, swaps, and working set. We use these words as the backbone of a life spent defending something. You use them as a punchline.”

I saw code that looked like this today:

class Class1 {
  static void Foo(object @this) {
    Console.WriteLine(@this);
  }

  static void Main(string[] args) {
    Foo(“hi”);
  }
}

It freaked me out, but it’s completely legal and kinda cool…

Congrats to the VC++ 2005 team for a write-up like this!

“The truth is that this new development in C++ seriously undermines the justification for C# as a language. C++ programmers yet to learn C# simply don’t need to now. What’s the point? They will find the full productivity of Visual Studio 2005 right there at their fingertips supporting the language they know and love. Why should they move to something that is slower and less feature rich?”

He goes on with choice words about those of us that use C# as either “poor folk who have already invested time in it,” “Java types moving to .NET and smart enough to avoid J#” or “dev-celebs and style gurus will realize that it’s in their interest to keep pushing the C# fashion wagon.” I don’t know which camp I fall into, but I love the phrase “dev-celeb!” : )

I remember being in a conference room many years ago with about 10 members of the VC++ team on one side of the table and me on the other with them drilling me for about an hour on what would it take for me to love C++ and give up C#. I asked for the power and performance of C++ and the simplicity of C#. According to The Grumpy Programmer, they’ve not only delivered on this promise, but

“the painful, balls-on-the-table truth is that C# has lost its point.”

Luckily, no one asked me to put any of my body parts on the conference table that day, but you gotta love a guy that can turn a phrase like that. : )

Apparently in Whidbey, “dumpbin” (and some other tools that were merely wrappers around link) has been dumped. To get to it now, do “link -dump -dumpbin_options” e.g. “link -dump -exports” does what “dumpbin -exports” used to do. In fact, if you just do “link -dump” the usage you get is labeled as the dumpbin usage. : )

BTW, it looks like “lib,” while still there, is also “link -lib” and “editbin” becomes “link -edit.”

[via Brent Rector]

Imagine the following C program:

// cmdio.c
#include <stdio.h>

void main() {
  char s[256] = "";
  printf(">");
  scanf("%s", s);
  printf("%s\n", s);
}

If I run this from a command shell and I enter “hi” [Enter], it looks like this:

C:\>cmdio.exe
>hi
hi

If I run it again using “lo” [Enter] this time, it would look like this:

C:\>cmdio.exe
>lo
lo

Here’s the thing that blew me away. Anytime I run it after the 1st from the same cmd shell, I get history! For example, running it a 3rd time and pressing [Up Arrow][Enter] gives me this!

C:\>cmdio.exe
>lo
lo

The up and down arrows work, F7 works, F8 works, they all work! When the heck did the shell start keeping track of per sub-command histories and why haven’t I noticed it ’til now?!?

First there was case-correction, now VB programmers in VS 2005 beta 2 get grayed out members in intellisense if they set their ClickOnce properties below FullTrust. Cool!