Friday, June 10, 2005 10:24 AM
Woe. Woe, I say. Woe! To Thee! If thou wouldst assay to run an XSL transform with the .NET XslTransform object. And a knight recreant would I be to keep my tongue caged within its red and toothy prison over it. As 'twere.
Simply put, the .NET XslTransform class is not MSXML based. MSXML is fast. XslTransform is slow. Particularly with transforms of larger XML docs - performance gets worse the larger the XML input is. Supposedly this will all go away with .NET 2.0.
If you pass WebPublisher an XSL document with a query, you're in no trouble, since WebPublisher is using MSXML.
Keywords: tortoise, hare, woe
Thursday, June 09, 2005 10:27 AM
It's hard to rant when words are inadequate. Musing is similarly right out. This is exactly why Hallmark is doing a roaring trade in prefabricated sentiment.
Nathan Mayr, a friend, a fiendishly genius developer, and someone I looked up to (he was taller than me) has died and silence is all that comes out.
Tuesday, May 24, 2005 3:23 PM
In Canada, we celebrate Victoria Day every year on the Monday preceding May 25th, in memory of Queen Victoria (1837-1901). I'm not sure why. In Victoria, where I live, the conjunction of the Day with the eponymous City means we must have a parade. We have had for 107 years. "Every minute of this 2-1/2 hr parade will leave you entertained" touts our official tourism website. Well, whatever. Somehow I end up watching every year anyway.
A lot of American high school marching bands show up for the event, and they're mostly really good, for high school students trapped in polyester. Part of the fun (every minute, folks, EVERY MINUTE) is to try and guess what the hell tune they're playing. Sometimes it's obvious ("Louie, Louie"), sometimes it's more challenging, as you strain your "top of the pops" trivia skills to the limit. One in particular had me stumped. The tune was tantalizingly familiar - I could even hum along - but I couldn't for the life of me name what it was. My sister didn't know. My wife hadn't a clue. I was like, I KNOW THIS, but I couldn't identify it. Until suddenly, as the last rank of tubas was passing, I had it: Ozzy Osbourne, "Crazy Train".
Ozzy Osbourne? OZZY? OSBOURNE!? Now, I love Ozzy, but for me, that song is a symbol of my long-hair headbanging days. You know, rebellious youth and loud, possibly Satanic music. And here they are, these kids, turning my rebel anthem into an easy-listenin' family-parade-day brass-n'-woodwinds favourite. I hated every one of 'em. Then I remembered who was wearing the burgundy and gold, one-size-fits-none bibbers and jacket with matching spats for a two mile stretch on a public street in front of 90,000 spectators. And felt a lot better.
Friday, May 20, 2005 10:20 AM
Loose and lose are DIFFERENT words in the English language. For the love of GOD, if I see one more person use "loose" when they mean "lose", I'm going to gnaw a hole in my belly and pull out enough intestine to strangle myself out of sheer blighted hope in the human condition.
It's because yesterday I was using a third party control for a popup calendar. The control itself is great, and I was perusing the list of control properties, when what to my wondering eyes did appear, but the CalendarPopup.EnableLooseFocus property. The say what? Uh... some kind of focus where the rivets have joggled free and are rattling around because I prefer that over a TIGHT FOCUS? AAAAAAAAAAAAAAAAHHHHHHHHHHHH!
Doesn't the Law of Grammatic Entropy which governs such words as qwik, ez, and donut (nee quick, easy, and doughnut) DEMAND that longer words collapse to shorter ones due to the overwhelming pressure of human laziness? How then the extra "o"? It's actually more work: the finger expends double the calories as it redundantly hammers the key. Obviously the Grammatic Entropy law is being counteracted by the Law of Orthographic Horsepower which says that if one letter is good, more must be better.
Next on the block: its versus it's.
Friday, May 06, 2005 1:38 PM
With ASP.NET set to impersonate a non-anonymous Windows account, I found the Inmagic ODBC driver flipped a henry when asked to perform a SELECT MAX statement. The error returned was "ERROR [S0000] [Inmagic, Inc.][DB/Text ODBC Driver]Unable to do ORDER BY".
It turns out that read/write permissions on the Documents and Settings\[machinename]\ASPNET\Local Settings\Temp folder are required (this is an XP machine I'm talking about). (Thank you Filemon.) I assume the ODBC driver requires some workspace in order to sort the records and pick the most maxest one. I don't know if this is the case with any ORDER BY clause or what. The ASPNET account has full control of that temp directory by default. Giving the Users group read/write access cured this otherwise intractable phenomenon (the Windows account in question was a member of the machine's Users group).
If you're wondering how to flip a henry, use your imagination.