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.

1. Wake up!

2. SharePoint for ASP.Net Developers (It’s gonna be ok, really)

3. Who are you?

4. Me: LiquidHub Solution Architect SharePoint Architect Developer Father Virginia Tech Hokie Gamer World Famous Jungle Cruise Skipper (ret.)

5. SharePoint for the ASP.Net Developer What’s different? What’s the same? What tools do I need? 10 things every SharePoint developer should know How to get your code rejected by your SharePoint Architect(s) Resources

7. Federated Search

8. Excel Data Services

9. Business Connectivity Services

10. Single Sign-On

12. Access Services

13. Scalable Service Hosting

14. Visio Workflow integration

16. 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

19. Things every developer should know

20. 10 Things Every SharePoint Developer Should Know Whenever possible, avoid creating custom Site Definitions

21. 10 Things Every SharePoint Developer Should Know Solution packages are NOT side-by-side, versioned deployments

23. 10 Things Every SharePoint Developer Should Know Out of the box master & layout pages should never be modified

24. 10 Things Every SharePoint Developer Should Know JavaScript and Publishing Content Pages do not play well together OK (In a Content Editor Web Part): <script type="javascript">…</script> Not OK (CEWP or page content): <a href="#" onclick="javascript: …">link</a> List data is always stripped of JavaScript

26. 10 Things Every SharePoint Developer Should Know Many of the out-of-box web part classes are inheritable (but not all)

27. 10 Things Every SharePoint Developer Should Know The rules for proper disposal of SharePoint objects isn’t cut & dry – but there is help. SPDisposeCheck

28. 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

29. Resources SPDisposeCheck Utility http://code.msdn.microsoft.com/SPDisposeCheck StackOverflow/SharePointOverflow http://stackoverflow.com http://sharepointoverflow.com Twitter (really) RSS feed for tweets w/ SharePoint links: http://hrl.mn/SPTweetLinks Your local SharePoint User Group

30. Photo Credits http://www.flickr.com/photos/matthewebel/4542976737/ http://www.flickr.com/photos/photojonny/2268845904/ http://www.flickr.com/photos/damaradeaella/2822846819/ http://www.flickr.com/photos/jbtaylor/5304492399/ http://www.flickr.com/photos/drsethery/5359342958/

32. You can find me at:

33. Blog: http://greghurlman.com

34. Twitter: @ghurlman

35. Email: greg@greghurlman.com

36. Princeton Area SharePoint User Group

37. SharePoint Saturday New York (July 30, 2011)

39. One more thing…

40. Packers win, 24 - 21