Scott Hanselman's ComputerZen.com

Maybe this is obvious, or maybe I'm insane, but it seems to me (from the outside)  that Apple's new Safari WebBrowser is just a Apple-Branded version of the Mozilla Project's Phoenix Browser.  The position of the built-in Google text box next to the address bar is what tipped me off.  Maybe I'm wrong.

I've been a IE user (who isn't?) forever, although I've made half-assed attempts to switch as I saw something better come out.  I tried Netscape 6, Mozilla at various phases, all the early Gecko-based stuff.  I even went through my whole "Opera" phase back when it still fit on a floppy. 

But, I'm using Phoenix full time now on Windows XP Pro.  I even make the scary "default browser" final step.  IE doesn't even show up on my desktop.  It's an odd feeling.

Also interesting to me is that we spent the better part of ten years putting bells and whistles (and menus and buttons and hot keys) into Browsers, and now we are stripping them out. 

I mean, really, Home, Forward, Back, Google. How hard is that?

Am I missing something?  Where in my Windows .NET Server 2003 RC2 install is Active Directory Application Mode (AD/AM)?  Certainly not in the AD Wizards...or the help...or the CD? Anyone?

Since ASP.NET "speaks" named pipes with IIS...

• Download the FileMon utility from SysInternals
• Run FileMon and select Drives->Named Pipes only
• Set from Edit->Filters/Highlights to asp*.exe;inet*.exe to show only the named pipes between ASPNET_WP.EXE and INETINFO.EXE.
• You should see a periodic write from ASPNET_WP.EXE and read from INETINFO.EXE (some ping mechanism)
• Kill ASPNET_WP.EXE and you'll see the intital startup and handshake as inetinfo starts ASPNET_WP.EXE up again

Compact Framework goes 1.0!

I must have missed this - it's dated Jan 3. Windows CE .NET 4.1 .NET Compact Framework 1.0 RTM Update  (from The Furrygoat Experience)
[The Furrygoat Experience][Managed Space]

Recently I needed to inspect a bunch of Visual Basic 6 DLLs (binary) that I [gulp] didn't have the source for. I wanted to see if they were marked in Project Properties when they were compiled as "Retain in Memory" and "Unattended Execution" (Note KBs Q264957 and Q241896) At any rate, a friend pointed me at this COMPLETELY UNSUPPORTED TOOL that you can run from the command-line and it will tell you if your VB6 Binaries are marked appropriately for use in COM+.