7. To Virtualize or not?
With Virtualization Without Virtualization
Need 64 bit guest capable VM
software
No virtualization software
required
Requires more memory and disk
space
Requires less memory and disk
space
Prerequisite installer installs
everything (almost)
Prerequisites have to be installed
manually
Can be shut off when you are not
using it
Services are always running
unless you shut them off
Easier to restore when you mess
up
8. What else do I need?
• Windows Server 2008 R2 (or SP2) x64 / Windows 7 x64 for
native installs
• SQL Server 2008 R2 (or SP1+CU2) x64 / SQL Server 2005 SP3
x64
• Virtualization Software (if virtualizing) – Oracle VirtualBox,
VMWare Workstation, Hyper-V, etc.
• Complete requirements at
http://technet.microsoft.com/en-us/library/cc262485.aspx
9. SharePoint Basics
• Farm (SPFarm) – Represents the collection of servers of the
SharePoint deployment
• Web Applications (SPWebApplication) – Typically one or
more of these maps to a web site in IIS (i.e.: Port 80)
• Site Collection (SPSite) – Will have at least one. Groups sites
together
• Site (SPWeb) – Represents a site or subsite in a Site
Collection. Contains pages, lists, etc.
• Feature – Allows code and SharePoint changes to occur at
the click of a button
• Solution (.wsp) – CAB file used for deployment
10. SharePoint Root Folder (aka 14 Hive)
• Location of most key SharePoint files: C:Program FilesCommon
Filesmicrosoft sharedWeb Server Extensions14
• Called 12 in WSS3
Folder Description
CONFIG
Contains partial
trust configuration files
ISAPI
Binaries and SharePoint Web
Services
LOGS
Error Logs (look here first when
you get a strange error)
TEMPLATECONTROLTEMPLATES User Controls
TEMPLATEFEATURES
SharePoint Features (turns
functionality on and off)
TEMPLATEIMAGES MainImages Folder
TEMPLATELAYOUTS Pages and Styles
11. Solution Types
• Farm Solution – Same type of solution used in WSS3. No
security restrictions unless using partial trust
– Can be deployed with Full Trust or Partial Trust
• Sandboxed Solution – Deploys to the site collection with
security limitations
– Cannot elevate privileges
– Can only access artifacts in the site collection it was activated
on
– Administrators can restrict the amount of resources available
– Ideal for shared hosting environments / cloud
12. Visual Web Part
• A glorified ASP.NET User Control with a Web Part wrapper
• Built with a designer
• Only available in Farm Solutions (third party options
available for Sandboxed)
14. SharePoint API
• SPContext – Used to get reference to the current site or site
collection
• All uses of SPSite or SPWeb must be disposed (use a using
statement)
• Most collections do not have an “Exists” method
– A few if them do now in SharePoint 2010
• Most objects require a call to .Update to save any changes
made
• Some API calls require elevated security – Pass a delegate to
RunWithElevatedPrivleges
16. Deployment
• No manual configuration or third party add-ons required
• Visual Studio builds features and solution package files for
you
• Visual Studio deploys packages directly to SharePoint server
• Solution packages can still be deployed to other servers via
PowerShell
17. Resources
How to Build and Deploy a Web Part in SharePoint 2010
http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2010/02/1
5/intro-to-sharepoint-2010-development-how-to-build-and-deploy-a-web-
part.aspx
How to Build and Deploy a Web Part in WSS3
http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/10/2
2/intro-to-sharepoint-development-how-to-build-and-deploy-a-web-
part.aspx