May 22, 2007, 1:06 p.m.
Wow, this is cool. Double-click any of the words in a New York Times article and it pops up a window with results from a dictionary, encyclopedia and thesaurus. It even appears to do a little parsing, as clicking on "South Dakota" will pull up the entry for the state.
April 25, 2007, 2:25 p.m.
<a href="https://www.gizmocall.com/">Wow, this is cool</a>. Haven't used it yet, the room I'm currently sitting in doesn't have coverage.
April 25, 2007, 12:35 p.m.
You may have added directories containing .NET assemblies to the registry key HKLM\Software\Microsoft\.NETFramework\AssemblyFolders so .NET can find them. Unfortunately, <a href="http://www.codeplex.com/MSBee">MSBee</a> does not look here. If you haven't heard of MSBee, it's a Microsoft tool that lets you target .NET 1.1 using Visual Studio 2005. Add the following XML to MSBuildExtras.Fx1_1.Common.targets in Program Files\MSBuild\MSBee: <pre><GetRegistryValue RegistryKey="Software\Microsoft\.NETFramework\AssemblyFolders\Cisco" BaseRegistryKey="HKEY_LOCAL_MACHINE" ContinueOnMissingKey="true"> <Output TaskParameter="RegistryValues" ItemName="VisualStudioPIASearchPaths" /> </GetRegistryValue></pre>
April 17, 2007, 9:41 a.m.
With the new network configurations I've been using for the new job, I figured I'd run the DSLReports speed test again. This seems a little fast, though: <a href="http://speedtest.dslreports.com"><img border="0" src="http://www.dslreports.com/im/28276994/9958.png" /></a>
April 9, 2007, 9:11 a.m.
<a href="http://www.componentsoftware.com/Products/Converter/">Conversion tool</a>
Feb. 26, 2007, 11:13 p.m.
On a somewhat related topic: <ul> <li><a href="http://en.wikipedia.org/wiki/Dublin_Core">Dublin Core</a></li> </ul>
Feb. 26, 2007, 8:21 p.m.
With the new camera, I've <strong>really</strong> started taking a lot of pictures. I've been dumping them onto a Windows machine and using the Explorer "publish to the web" feature to upload them to the PHP gallery at <a href="http://www.thrall.net/gallery">thrall.net</a>. This works ok for now, but I'm thinking there's got to be a better way on both the client and server sides. I haven't figured it out, but consider this the beginning of a search for the client side. <ul> <li><a href="http://perso.orange.fr/pierre.g/xnview/enhome.html">XNView</a></li> <li><a href="http://www.f-spot.org/Main_Page">F-Spot</a></li> <li><a href="http://ktown.kde.org/kphotoalbum/">kphotoalbum</a></li> </ul>
Dec. 15, 2006, 11:44 a.m.
Huh, I had never given much thought to spec'ing power supplies before. <a href="http://www.byte.com/documents/s=9988/byt1165675841265/1211a.htm">This article in Byte by David Gilbert</a> is a great read on how to do it.
Oct. 5, 2006, 4:13 p.m.
There are a few different ways to get the local IP address. Here's <a href="http://www.codeproject.com/KB/IP/obafindingipinformation.aspx">a good article</a> on three different methods.
Oct. 5, 2006, 4:03 p.m.
Both System.Environment.UserName and System.Security.Principal.WindowsIdentity.GetCurrent().Name return a Windows username. What's the difference, other than the fact that the second version returns the "full" version (domain\username)? From the documentation: System.Environment.UserName "gets the user name of the person who started the current thread." System.Security.Principal.WindowsIdentity.GetCurrent() "returns a WindowsIdentity object that represents the current Windows user."