A lot of places are noting the release of a service pack for WSS, but the Admin Guide has been updated as well.

Windows SharePoint Services Administrator's Guide

Weather Forecast ASP.NET user control from Mikhail Arkhipov

When you're incapable of providing leadership or exercising good judgment, substitue an inflexible policy.

Bob Lewis, “KJR” Archive, 8/16/2004

I often use a web page to convert C# code to VB to help me understand it. Sometimes, that is overkill when trying to understand a keyword or two.

MSDN has this page to help in this situation: Keywords Compared in Different Languages

A community site, Attune Systems, has the PowerSearch tool installed. Type “experts” in the search box (top-right for the unfamiliar).

My debugging method of choice is the ASP.Net trace feature. In web config, I set the trace options:

    <trace enabled=”true” pageOutput=”true” localOnly=”true” />

This will dump a bunch of information at the bottom of the page. (WARNING: Do not do this on a publicly accessible machine. It will compromise security.)

In my web part, I include a call to Context.Trace.Write at the beginning of each routine. In the catch blocks, I call Context.Trace.Warn(ex.ToString). This puts the entire exception into the trace output. Plus, it avoids the WSS error page (“The [Name] Web Part appears to be causing a problem.“)

If you run SharePoint on your LAN, you may not notice that the pages are a bit large (when you include the script files). If you have external partners, or perhaps run SharePoint on a hosted server, you should read Maurice Prather's write-up.

Soon after receiving the PDF file from the marketing/design consultants, I was given a deadline of August 2nd!  So, the blogging didn't work out as expected.

The demo went well, and the site goes live next week. I'll try to get some comments about my experience posted.