Friday, June 04, 2004

To finish a point I was making earlier (and he quotes (like anyone cares (oh dangit, did the French overparenthesizing again)):


I also have oodles of old material from the long-lost website to recycle. was, in a way, my blog before blogging existed. I abandoned it because I was too far ahead of my time (okay, life happened and I did not have time... get off my back, please). However, it was very, very popular with Microsoft employees.

[slash quote]

When I had my own site, (only taking it because was unavailable... and oh goody goody goody, look at what was blocking my registration... and I begged this guy, but noooo, he had plans; wait, did I mention there are some people that need to be stabbed to death with a piece of pocket lint (yes that would take a few weeks -- that's the entire fershnikkedthe point, dangit)), so to remind you, when I had this site to exercise my ASP (no .NET) skills, I was also a programmer.

Well, the emphasis on that just lost its way, did a pirouette and landed four-square on the wrong friggin' part of the sentence.

The point being that when I was blogging avant la lettre, I was also doing a lot of Beta Testing. From Visual Basic 4.0 until Visual Basic .NET 2002, I was involved from the first betas onwards. I hosted TUSUC, my Visual Basic .NET 2002 Beta 1 version of "The Ultimate Silly Unit Converter". And if I say so myself, it friggin' rocked. OSDN or SourceForge be damned, nine people were contributing to the source code, ON A BETA 1 RELEASE, ON AN APPLICATION THAT WOULD NEVER MAKE A DIME, OUT OF LOVE OF THE DEVELOPMENT ENVIRONMENT. I would get between 60-150 distinct sessions daily out of The only person I could identify as having visited my site was Peter Torr (who by now has a much better blog than my site ever was). Life was good. People at Microsoft were paying attention to me and (I like to think) liked what I wrote (because, as the weblogs revealed, people read EVERYTHING on my site once they got interested...). My life was good. I was half an inch a way from an invitation to Redmond. I felt the way Rory must feel. Or maybe that's just my inimitable modesty attempting to draw a comparison between someone as lofty as I am and him, being witty and at least moderately accomplished and all. Yes, that is sarcasm. And yes, that means I would dearly love buying Rory a few bottles of things that are bad for the liver if he ever gets in the general vicinity of Sacramento.

Anyway, between Beta 1 and Beta 2, they did the AndAlso/OrElse thing for Beta 2 (I will blog about this later)... and I was done. Man, stick a fork in me and roll me over and I was done. That was insulting to every single VB programmer in the world. Like, um, "we think this is just waaaayyyy too difficult for you, so we'll mess up any good this might have for you" kind of insult. (Okay, they had some points why they changed it, not in the least the general Internet outcry -- but they listened to the wrong people: people who were about to abandon VB anyway). Nowadays, give me one, single advantage of VB, Paul Vick. One that is not IDE-related.

I dare ya. (Actually, I want you to prove me wrong here. I have 9 years of VB experience, and it breaks my heart having to leave it lately -- there's some SERIOUS emotional investment here! The things I wrote in VB 3.0 and 4.0...).

Oh man, am I mad now. There were 6 more paragraphs after this, but blogger decided to die. Anyone out there with real blog hosting that doesn't die? And has RSS?

Remember that fork? It's in me now. Bleh. Done.

SQL Server 2000's IsNumeric LIES!

Quoth the Books Online:

ISNUMERIC returns 1 when the input expression evaluates to a valid integer, floating point number, money or decimal type; otherwise it returns 0. A return value of 1 guarantees that expression can be converted to one of these numeric types.

[ emphasis mine ]

Now try this in Query Analyzer:

Select IsNumeric('.')

...which returns 1. So, for bonus points, what does this do?

Select Cast('.' As Numeric) error. Wonderful. Lies, lies, lies. This function could be in the Bush administration!

Thursday, June 03, 2004

Visual Studio 2003 or 2005?

So everyone is abuzz over the Visual Studio 2005 Team System. Imagine my surprise to see, in Visual Studio 2003, in the C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\VS SCC\1033 folder, VisualStudioTeamCoreUI.Dll...

Guess they've been working on it for a while.

Actually, the most amazing thing is that the name hasn't changed in over two years! Is the marketing department ill, or were they the first against the wall when the revolution came(*)? Of course, that's assuming all kinds of things, but speculation is fun.

Even funner would be to get an answer from someone on the Visual Studio team, but the odds of them -- actually, anyone -- finding this blog are not that good.

(*) Yes, that's a Hitchhiker's Guide To The Galaxy reference.