Michael Earls, cerkit.com founder and .net super-guru, advised me to use spaces rather than tabs in my source code indention.  He also suggested using 2 spaces rather then the stadard 4.  The reasoning behind this is to allow consistent formatting no matter where the code gets moved to or viewed from.  Notepad, html posts, word documents, articles, etc.  The upper echilon find this to be very important.  I aspire to one day find this to be more than just a little helpful.

I set up my Visual Studio to operate this way and worked with it for about a month.

While I do like the 2 space compactness, Visual Studio tends to get confused with the spaces.  I find myself re-formatting manualy every now and again.  ctrl-k, ctrl-f works about 70% of the time. 

I read about a vb shorcut to untabify.  I quickly looked into VS.net to find these commands unmapped in my shortcuts menu. 

I mapped it to ctrl-k, ctrl-1  and ctrl-k, ctrl-2 respectively for tabify and untabify.  There are also commands for Edit.ConvertTabsToSpaces and Edit.ConvertSpacesToTabs.  They appear to do the same thing. 

Check it out!  I have set my VS.Net back to tabs and will now use these commands when copying code for posts, artcicles, emails, etc...