Ok, so I'm more than a couple weeks into writing the SharePoint 2007 book and I have to say writing code against SharePoint 2007 with the 2.0 Framework ROCKS!

There are a lot of things that are really cool about developing web parts that will make life easier in both development and maintainence.  SharePoint 2007 Web Parts are actually built on top of the ASP.NET 2.0 Web Part Framework, which makes development a lot easier that it was with SharePoint 2003.  There are two classes that you can use as bases for your custom web parts: System.Web.UI.WebControls.WebParts.WebPart (ASP.NET 2.0) and Microsoft.SharePoint.WebPartPages.WebPart (SharePoint).  The Microsoft.SharePoint.WebPartPages.WebPart class actually inherits from the ASP.NET 2.0 web part and ensures seamless uplevel support between ASP.NET 2.0 web parts and SharePoint web parts. Now you might be asking when should you use on e over the other?  Actually, you should use th ...

Rob at www.gottabemobile.com has posted a cool video of the new Tablet Input Panel that ships with Windows Vista. Very similar to the one from Windows XP Tablet PC edition with SP2 but the best new feature I like is being able to highlight regular text and open it in character recognition mode in the input panel. Allows for easy editing of typed text using ink. Check it out http://www.gottabemobile.com/VistaTIPSoftwareInkShow.aspx.

Also check out TEO 3.0 from Josh Einstein at http://www.tabletoutlook.com/. Nice add-in for Outlook to make it much easier to use it on the Tablet PC. Josh also helped me a great deal on my current project and some of the best ideas we implemented in our own ink controls we stole (with his permission) from him.

I know Sysinternals Process Explorer has been recommended in several blogs for quite some time. While most developers are familiar with this Task Manager replacement, few seem to leverage all it has to offer. Where I find it most useful is in the Process View (you have to double click the process to get there). Once there check out the .NET tab (.NET assemblies only) which provides some great information about what the process is doing. I personally like to monitor the .NET CLR Data information to help me better understand memory usage during runtime. If you have a memory leak in a .NET assembly this can be extremely helpful. I used it to monitor Garbage Collection and Generation Heap Size as I navigated one application and found clues which assisted me to eliminate a nasty leak. If you are not familiar with how the Garbage Collector operates this a good way to learn.  I also recommend you check out this