Note: I'm still alive - it's just been hectic with tax season and all. Updates will be forthcoming :-)
Automation Samples for Visual Studio .NET 2002 - particularly this one: "This macro project fetches Microsoft Outlook tasks and puts them in the Visual Studio Task List. It then keeps those tasks synchronized between Visual Studio and Outlook whenever you change task descriptions or mark tasks complete."
I modified the code a bit to have it import from a subfolder - VSTasks - of the main tasks folder so that, for instance, reminders to renew library books or pick up dry cleaning don't end up in VS.NET. (Remember: the task list is different for each solution, so use this macro wisely.)
'Get TaskItems list from Outlook
app = GetObject("", "Outlook.Application")
namesp = app.GetNamespace("MAPI")
oltaskfolder = _
namesp.GetDefaultFolder( _
MSOUTL.OlDefaultFolders.olFolderTasks)
'here is my new line
oltaskfolder = oltaskfolder.Folders.Item("VSTasks")
oltaskitemlist = oltaskfolder.ItemsGetting the Most Out of Visual Studio .NET - the toolbox.tbd file where the code snippets are contained is stored (i.e. C:\Documents and Settings\Administrator\Application Data\Microsoft\VisualStudio\7.0) so that you can back it up/copy it to other machines and keep your code snippets safe.
ADO Data Type Mapping - shows the ADO Data Type mapping between Visual Basic, Access, SQL Server, Oracle, and the .NET Framework
The Code Project - best ASP.NET site I've found
Microsoft Consulting Services Naming Conventions for Visual Basic
FxCop: FxCop is a code analysis tool that checks .NET managed code assemblies for conformance to the Microsoft .NET Framework Design Guidelines.