SharePoint Stuff
2007 Books
2003 Books
2003 Errata
2007 Errata
Downloads
    
As I work with customers and receive feedback, I will post errata to this area to improve the accuracy of the book. If you find an error in the book, please contact me to add it to this page. The last errata update was 21 March 2007.

Errata for the C# version

  • Page 10, 2nd paragraph: change "SharePoint Portal Server (SPS)" to simply "SharePoint".
  • Page 164, Note: The note states that STP files are always the same as customized pages. However, STP files will remain uncustomized as long as they haven't been edited with the SharePoint Designer prior to being saved as a template.
  • Page 247, 1st paragraph: states "Unfortunately, there is no code-behind model...". Well, actually there is something of a code-behind technique that inherits from the LayoutsPageBase class and produces a pre-compiled assembly. I have a complete blog entry on this topic here.
  • Page 271, In order for the activity to work in the SharePoint Designer, you must also make an entry in the AuthorizedTypes section o.
  • Page 273, Exercise 7-1: Note: This exercise requires the Enterprise version of MOSS to complete. WSS cannot utilize InfoPath forms in the workflow.
  • Page 425, Listing 11-8: Replace the comment "//Code Goes Here" with the following

              using(SPSite site = new SPSite(
              SPControl.GetContextSite(Context).ID))
              { //Code Goes Here}

Errata for the VB.NET version

  • Page 10, 2nd paragraph: change "SharePoint Portal Server (SPS)" to simply "SharePoint".
  • Page 164, Note: The note states that STP files are always the same as customized pages. However, STP files will remain uncustomized as long as they haven't been edited with the SharePoint Designer prior to being saved as a template.
  • Page 247, 1st paragraph: states "Unfortunately, there is no code-behind model...". Well, actually there is something of a code-behind technique that inherits from the LayoutsPageBase class and produces a pre-compiled assembly. I have a complete blog entry on this topic here.
  • Page 273, In order for the activity to work in the SharePoint Designer, you must also make an entry in the AuthorizedTypes section o.
  • Page 275, Exercise 7-1: Note: This exercise requires the Enterprise version of MOSS to complete. WSS cannot utilize InfoPath forms in the workflow.
  • Page 429, Listing 11-8: Replace the comment "'Code Goes Here" with the following

              Using Site As New SPSite( _
              SPControl.GetContextSite(Context).ID))
              'Code Goes Here
              End Using