Hi Gareth, good catch. I didn't explicitly mention that the software listed for the Host machine on p. 35 (including VSeWSS) might be used in the steps. Luckily, the steps on p. 51 are the same whether creating a class library (the way I personally start building a web part) or a C# SharePoint web part.
To take a tangent from remote debugging into creating web parts. . .
While it's true that that VSeWSS (or one of several CodePlex projects) is required to get any "SharePoint web part" option to appear when creating a VS project, these days I recommend against the project templates provided by either VSeWSS for Visual Studio 2005 or those included in VS 2008. This is mainly because they're geared for local (F5) development, don't give a proper variety of deployment options for Feature or Solution generation, and require people you share your source with to also have either VSeWSS or VS 2008 installed.
Instead, check out STSDEV on CodePlex (http://codeplex.com/stsdev
), which provides effective templates for many SharePoint objects and works great with WSPBuilder (http://codeplex.com/wspbuilder
) for generating solutions.