Topics du Jour: Whidbey Console applications; Making mistakes; not watching the super bowl; Brewing Sake and making Yakisoba; Finding the Right Book; Geocoding meets Photography; Free modern programming course; Beer prevents Cancer?; KbAlertz goes RSS; the daily pointer to Dana Epp; the bad (and good) effects the PC can have on a marriage; Oracle 10-G and WriteTheWeb.
Just in, but several sources are reporting that a new cumulative patch for IE will be release shortly. Thank goodness!
This one appears to fix the ability run a script in the local machine zone, the HTML Application “stomp over” problem and the URL obfuscation problem. It will also remove credential embedding in HTTP and HTTPs URLs. They say that MSXML for XMLHTTP since credential embedding won't be supported there either. Finally, theres a “refinement“ of the “navigation back to Local Machine Zone“ fix that was in the last patch.
Sounds like a good one to get into your deployment system ASAP.
I've mentioned in the past that I am working in earnest on an FAQ for Reporting Services, but some of the most F'ed A'ed Q;s are something like this:
Q. We're a “classic” ASP only shop using Windows 2000. Do we have to upgrade to .NET to use Reporting Services?
A. Yes and No. No, you don't have to stop writing ASP to using Reporting Services. The two will happily co-exist on the same server if you want. However, Reporting Services itself is a .NET-based application so you do have to have at least version 1.1 of the framework installed on the Report Services host. And, while you can write the reports themselves in any tool that generates a Report Definition Language (RDL) file, the one most of us will start with is one that integrates with VS.NET 2003.
Q. Can I write a report in HTML format and how do I upload it to the server?
A. Reports are expected to be in the form of Report Definition Language (RDL) files, not HTML.
Here's an updated list of the 50 "words" that seem to keep showing up in the Spam (UCE) that's still getting through to me. Although the volume of suspect messages decreased about 45% last month as we ratched the filters up, 325 chunks of Spam still made it through,