PDisposeCheck for SharePoint Developers has been released. SPDisposeCheck inspect your SharePoint assemblies to make sure you are code is disposing correctly

Link

The reason for the problem is that the GUID is the same as an existing site. You could either delete the old site or create a new web application and restore in that new one.

The Community Technology Preview release for Visual Studio 2008 extensions for SharePoint 1.3 is now publicly available on Microsoft Connect.

The CTP is available at: https://connect.microsoft.com/site/sitehome.aspx?SiteID=428

New Features in VSeWSS 1.3

• The extensions now install on x64 bit OS. Visual Studio 2008 and SharePoint must be already installed.
• Command Line Build option for TFS and MSBuild integration
• Separate WSP Package and Retract commands. You can now build the WSP without deploying it
• SPSolGen to Support Exporting from Content Management Publishing Sites
• New Item Template for RootFiles Deployment
• Automatically Remove conflicting existing features on development SharePoint server
• WSP View New Feature Dialog Improvements: scope, receiver checkbox, element checkbox
• WSP View can now be used to merge features and it blocks site features being merged into web features
• Allow adding separate binary files such as Workflow assemblies
• Some refactoring allowing for Web Part renaming and removing lines from feature.xml Item Removed
• Allow selection of GAC or BIN deployment for Web Part Project not including CAS generation
• Increase visibility of hidden features that VSeWSS creates
• Add fast update deploy for DLL only or file only changes to solutions
• Numerous Bug Fixes and improvements to error messages

I spent most of this year doing SharePoint development and Architecture. My role at my company will probably continue along that path and perhaps even more so.

Resolutions for 2009

Spend more time outside and SharePoint of course.