160 likes | 303 Vues
Join Todd Kitta in this insightful presentation from September 2008 at the Saint Louis SharePoint Users Group, where he shares best practices for SharePoint development and deployment. Learn about crucial features, solutions, and key tools to simplify SharePoint project workflows. Todd, a SharePoint Architect at Covenant Technology Partners, discusses the importance of concepts like Features, Solutions, and Feature Receivers, while providing resources and hands-on demos to enhance your SharePoint proficiency.
E N D
SharePoint Development/Deployment Best Practices Todd Kitta September 2008 Saint Louis SharePoint Users Group
Agenda • Introductions • Features • Solutions • Helpers • Demo
A Little About Me • Husband & father of 2 beautiful girls! • SharePoint Architect for Covenant Technology Partners • SharePoint Podcast – www.mossgonewild.com
SharePoint Development Overview • SharePoint == Big ASP.NET Application • SharePoint v2 (WSS 2.0, SPS 2003) • SharePoint v3 (WSS 3.0, MOSS 2007)
You should never have to manually do anything on the web front end!
Features • Distinct piece of deployable functionality, can be turned on and off • Scoped at a Farm, Web Application, site collection (Site), or site (Web) level • Feature.xml • Elements Manifest(s) • Reference wss.xsd (C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML\wss.xsd) • Goes for all other XML files as well…
Things you can do with Features • Create new site columns and content types • Create new list instances with pre-populated data • Associate a content type with a list • Deploy a custom workflow • Add a link to any ASPX page from the site menu • Deploy a new site page • Millions of other things…
Feature Receivers • If you cannot do something in your Feature.xml or Elements.xml, you can do it in code! • Other web.config modifications • Setting lookup column references for lists you are creating in the current feature(s) • Order of operations
Solutions • Manifest.xml • Know the DDF file • makecab.exe Solutions are just CAB files (with a WSP extension)
Things you can do with solutions • Deploy one or more features to a farm • Add a DLL to the GAC • Make web.config changes (SafeControls for example) • Deploy application pages, images, etc. to the LAYOUTS folder
Stuff to help you do this • STSDEV (http://www.codeplex.com/stsdev) • WSP Builder (http://www.codeplex.com/wspbuilder) • WSS Extensions for Visual Studio • VS2005: http://www.microsoft.com/downloads/details.aspx?familyid=3E1DCCCD-1CCA-433A-BB4D-97B96BF7AB63&displaylang=en • VS2008: http://www.microsoft.com/downloads/details.aspx?familyid=7BF65B28-06E2-4E87-9BAD-086E32185E68&displaylang=en
1 WSPBuilder 2 3
You should really feel comfortable with doing this stuff manually before using wizards or other helpers
Good Sources • SharePoint Developer Center http://msdn.microsoft.com/en-us/sharepoint/default.aspx • http://www.mossgonewild.com/