SharePoint for ASP.Net Developers
Upcoming SlideShare
Loading in...5
×
 

SharePoint for ASP.Net Developers

on

  • 2,233 views

The market share for SharePoint has grown in leaps and bounds over the last few years, leading to many developers being told that they are now SharePoint developers. Developing for SharePoint is a ...

The market share for SharePoint has grown in leaps and bounds over the last few years, leading to many developers being told that they are now SharePoint developers. Developing for SharePoint is a strange new world; we will cover what’s new, what’s the same, the top things that every SharePoint developer should know, and a few things to make every new developer’s life easier.

Statistics

Views

Total Views
2,233
Views on SlideShare
2,194
Embed Views
39

Actions

Likes
0
Downloads
28
Comments
0

3 Embeds 39

http://greghurlman.com 19
http://greghurlman.wordpress.com 19
http://ghamson.wordpress.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

SharePoint for ASP.Net Developers SharePoint for ASP.Net Developers Presentation Transcript

  • Hello!
  • SharePoint for ASP.Net Developers (It’s gonna be ok, really)
  • Who are you?
  • Greg Hurlman: LiquidHub Solution Architect SharePoint Architect Developer Father Hokie Gamer World Famous Jungle Cruise Skipper (ret.)
  • SharePoint for the ASP.Net Developer What’s different? What’s the same? What tools do I need? Top 10 things every SharePoint developer should know How to get your code rejected by your SharePoint Architecture group Resources
  • What’s different? You get a lot of functionality for free Authentication/Authorization Page Templating Workflow hosting/reporting Data storage You get a LOT of functionality for free Federated Search Excel Data Services Business Connectivity Services Single Sign-On Etc. LOT Metadata management Access Services Scalable Service Hosting Visio Workflow integration Etc.
  • What’s different? Website Structure Web Application -> Site Collection -> S.C. Root Web -> Subwebs Deployment Code -> Assembly -> Feature (usually) -> Package (.WSP) Fea⋅ture /ˈfitʃər/ -noun A functional unit of SharePoint functionality, scoped at a Farm, Web Application, Site Collection, or Web level Packages First added to the server farm Then, deployed to individual web applications
  • What’s the same? SharePoint is an ASP.Net app Web.config HTTPHandlers/HTTPModules Authentication Master Pages Web Parts == Composite Server Controls Inherit from System.Web.UI.WebControls.WebParts.WebPart Postbacks/Event Lifecycle Model
  • What tools do I need? Virtual Machine w/ Visual Studio, SQL Server, Active Directory, IIS, and MS Office running a server OS (64-bitfor SP 2010) Microsoft Office SharePoint Server 2007 SDK Enterprise Content Management (ECM) Starter Kit BDC definition editor Workflow samples and lots more SharePoint VS add-ins Windows SharePoint Services 3.0 Tools: Visual Studio 2008 Extensions, Version 1.2 (VSeWSS) WSPBuilder (for VS 2008/SP 2007 or VS/SP 2010) Visual Studio 2010 Tools for SharePoint Development (SP 2010 Only)
  • What every developer should know
  • The Top 10 Things Every SharePoint Developer Should Know Whenever possible, avoid creating custom Site Definitions
  • The Top 10 Things Every SharePoint Developer Should Know Solution packages are NOT side-by-side, versioned deployments
  • The Top 10 Things Every SharePoint Developer Should Know Web.config changes should be made in code, not by hand
  • The Top 10 Things Every SharePoint Developer Should Know SharePoint Designer can be the enemy of performance
  • The Top 10 Things Every SharePoint Developer Should Know Out of the box master & layout pages should never be modified
  • The Top 10 Things Every SharePoint Developer Should Know JavaScript and Publishing Content Pages do not play well together
  • The Top 10 Things Every SharePoint Developer Should Know Yes, you can have ASP.Net “yellow screen of death” callstacks on errors
  • The Top 10 Things Every SharePoint Developer Should Know There is a right and very wrong way to iterate through a SharePoint list
  • The Top 10 Things Every SharePoint Developer Should Know Many of the out-of-box web part classes are inheritable (but not all)
  • The Top 10 Things Every SharePoint Developer Should Know The rules for proper disposal of SharePoint objects isn’t cut & dry – but there is help.
  • How to get your code rejected by your SharePoint Architecture Group Don’t dispose of your SPSite and SPWeb (and related) objects properly The SPDisposeCheck utility is invaluable for this Use SPSecurity.RunWithElevatedPrivileges when unnecessary or just plain badly Log errors to whatever’s handy at the time Make changes to the web.config file without consideration for others
  • Resources SPDisposeCheck Utility http://code.msdn.microsoft.com/SPDisposeCheck StackOverflow http://stackoverflow.com/questions/tagged/sharepoint Twitter (really) RSS feed for tweets w/ SharePoint links: http://search.twitter.com/search?q=%23SharePoint+filter%3Alinks Your local SharePoint User Group
  • Questions?
  • Photo Credits http://www.flickr.com/photos/photojonny/2268845904/ http://www.flickr.com/photos/damaradeaella/2822846819/ http://www.flickr.com/photos/jbtaylor/5304492399/
  • Thanks for coming! Don’t forget your evaluations You can find me at: Blog: http://greghurlman.com Twitter: @ghurlman Email: greg@greghurlman.com Princeton Area SharePoint User Group SharePoint Saturday New York (July 30, 2011)