MOSS 2007

• Nov 2008 Patterns & Practices SharePoint Guidance
• Enabling SharePoint Intellisense in VS2008
• Developing and Using Web User Controls as WebParts in Microsoft Office SharePoint Server 2007(CodeProject)
• OBSOLETE: Windows SharePoint Services 3.0 Tools: Visual Studio 2008 Extensions, Version 1.2
• Visual Studio 2008 extensions for Windows SharePoint Services 3.0, v1.3 - Mar 2009 CTP
• SharePoint Manager 2007 (CodePlex)
• View MOSS 2007 or WSS 3.0 log files

Some MOSS Resources

• SharePoint Team Blog http://blogs.msdn.com/sharepoint
• Microsoft SharePoint Developers Portals
  • http://mssharepointdeveloper.com
  • patterns & practices SharePoint Guidance (CodePlex)
  • http://msdn.microsoft.com/en-us/office/aa905503.aspx
• Best Practices Resources Center http://technet.microsoft.com/en-us/office/sharepointserver/bb736746.aspx
• Developer Best Practices Resource Center http://msdn.microsoft.com/en-au/office/dd638301.aspx
• CodePlex http://www.codeplex.com
• William Cornwill's Blog http://www.codejedi.net

MOSS & Silverlight

• Silverlight Web Part in SharePoint (blogs.msdn)

SharePoint 2010 Resources

• mssharepointdeveloper.com
• SharePoint 2010 MSDN Reference pages
• SharePoint 2010 (Beta) Developer Center
• Microsoft SharePoint Server 2010: Deprecated Types and Methods
• SharePoint 2010 Dev Center Ramps Up, Adds BCS Resources (Visual Studio Magazine)
• Setting Up the Development Environment for SharePoint Server (MSDN, for SP2010) http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx
• SharePoint 2010 Training (Arpan Shah's blogs.msdn.com)
• SharePoint 2010: Professional Developer Evaluation Guide and Walkthroughs (Microsoft Document Download)
• SharePoint 2010 Books list

SharePoint 2010 & Silverlight

• Getting Started With Silverlight and SharePoint 2010
• Modify WebPart menu (Understanding and working with Web Part Verbs)
• Turn on the Developer Dashboard by running the following stsadm command:

stsadm -o setproperty -pn developer-dashboard -pv OnDemand

• In VS2010, can make the following changes to
  • Elements.xml: change the

    <Property Name="Group" Value="Custom" />

    to something other than Custom.
  • Webpart.webpart (webPartIcon is 16x16):

  <property name="ChromeType" type="chrometype">TitleAndBorder</property>
  <property name="CatalogIconImageUrl" type="string">_layouts/images/ContosoWebParts/WebPartIcon.gif</property>
  <property name="TitleIconImageUrl" type="string">_layouts/images/ContosoWebParts/WebPartIcon.gif</property>

• • Elements.xml, modify the URL attribute of File element to change the .webpart file name to ensure that it is unique. Do this by prepending the text value of "ContosoWebParts_" (ie Feature project name) to the beginning of the URL property value.