rawsoft: what about the swimsuit event:? ;)

Hmmm...*always*? Even for limited-set items such as gender, continent, blood type....? Seems like overkill to me.

These are good questions if you're hiring a developer for a Microsoft-focused shop, since the majority pertain specifically to either the .NET framework or SQL Server...but just because the interviewee can answer them doesn't mean they're the best candidate; it may just mean that they can retain MCSD study material. IMO good technical interviews also involve having the applicant step through code, write code (or pseudocode) and determine what a mystery program *does*.

Summary: "regions are evil since you can find stuff if you use ReSharper."

For those of us not willing (or able) to fork out $199 for an individual license, here's my advice: "go ahead and use regions. Like everything else, it can be abused. Use them wisely and apply corrective measures to junior developers who go region-happy."

Yep, that did it; I'm officially getting tired of SubSonic stories. :(

Bad submitter! No biscuit! ;(

The fourth mistake, of course, is developing an ASP.NET AJAX application in the middle of a land war in Asia.

It's a little squirrelly, but I don't know if I'd classify it as spam.

Sorry for sounding dense, but can somebody provide some context as to why this is a big deal? I'm not trolling, just uninformed.

I've been using GhostDoc for quite a while now. Excellent tool.

-1 for use of "M$" in a description. Let your audience reach their own conclusions without biasing them.

Wow.

What does this have to do with ANYTHING .NET-related?

I had Adblock running so I didn't see any advertisements...but at best this is a rather poor submission since all *I* saw was a code tree and absolutely no documentation or explanation. Completely useless if one didn't know what jQuery was or had never heard of the CSS Suckerfish menus.

A solid -1 if I could award it.

The Toolkit certainly has a bunch of useful widgets (I've been using it since March) but I really wonder 1) if we're going to see any substantial enhancements (as opposed to bugfixes) at this point and 2) .NET 2.0 and VS2005 will be cast aside in favor of .NET 3.5/VS2008 sexiness.

I've been using this for a couple of days, seems to work well.