Not sure how I missed....but here is a very handy new feature in VS2005.  Thanks to Jessica for pointing me to this.  Had I not stumbled upon this I would still be tracepoint-less. 

What is a tracepoint?  Well, in a nutshell.  It's like a breakpoint without the breaking part.  I can now use this to replace some of my Debug.WriteLine statements I use to debug in certain cases.  How to create a tracepoint:

1. Create a breakpoint as normal.
2. Right-click on the red circle indicating the breakpoint.
3. On the context menu, select When Hit.  There are other options as well, though they deal with breakpoint filters and such that I believe were in previous version of VS.
4. Fill in the dialog with whatever text you wish to print, you can even run a macro.
5. Close dialog, and red circle changes to red diamond indicating a tracepoint.

Very handy new tool and another reason I like VS2005 more and more each day.

Well, everyone else seems to be doing it.....  I come across quite a few links each day that interest me or I should investigate further.  Here is my attempt to list those ...  while I would like to say daily, I really doubt that will happen.  Here is my first short batch.

1. Reading Excel with ADO.NET - an interesting look into how ADO.NET handles Excel Docs.  Most interesting was how it guesses the data type of each column.
2. Creating a unique or semi-unique ID in .NET  - As I ran into a similar situation not too long ago (I actually stuck with using GUIDs as in this particular application, the length didn’t matter to me), this opens up a discussion on the GetHashCode() method used on a GUID to create a semi-unique ID.
3. Using ResolveClientUrl in markup – This comes in handy more than not, but it is invariably something I forget about each time.