How Asp.Net Developers Can Leverage Share Point
- 1. How ASP.NET Developers can leverage SharePointJeremy ThakeSenior Consultant, Readifyhttp://bit.ly/JTHAKERATE
- 2. AgendaIntroductionHow ASP.NET Developers can leverage itWhy Use It?MisconceptionsThe issues around leveraging itLimitations of OOTB areasWhen to stick with ASP.NETSummary
- 3. INTRODUCTIonHow ASP.NET Developers can leverage SharePoint
- 4. KEY DRIVERS FOR ASP.NET DEVELOPERSFastCompilingIDEPerformanceCan handle Complex ScenariosEasy to debugEasy to learnSimple APILots of learning resources
- 5. INTRODUCTIONAwarenessPeople hate it“It’s not open source”FrameworksOver engineeredDependenciesDevelopers like to write it themselvesFeel out of control
- 6. WHAT IS IT
- 7. HOW YOU CAN LEVERAGE ITHow ASP.NET Developers can leverage SharePoint
- 8. WHAT YOU NEEDWindows ServerVisual Studio 2005/8SQL Server Express/Std/Ent 2005/8
- 9. WHY USE IT?How ASP.NET Developers can leverage SharePoint
- 10. WHY USE IT?WSS is free!Most Enterprises own MOSSCommon User InterfaceCommon FrameworkCommon Data LayerCommon Disaster Recovery
- 11. WHY USE IT?Leverages already existing knowledge of ASP.NETIIS Web Applications and Application PoolsWeb.ConfigVisual Studio IDE (C#/VB.NET)Master PagesPage LayoutsWeb PartsUser ControlsSite ThemesXHTML/JavaScript/CSS
- 12. dEMO: CREATING WEB APPSHow ASP.NET Developers can leverage SharePoint
- 13. WHY USE IT?FrameworkSecurityComponent basedLoggingPersistenceArchitectureExtensionFile storageAudiences (MOSS)
- 14. dEMO: FEATURESHow ASP.NET Developers can leverage SharePoint
- 15. WHY USE IT?SharePoint ListsCRUDMetadataVersioningItem SecurityViewsEvent HandlersWorkflowSearchRecycle BinCustom Field ControlsIncoming email
- 16. dEMO: VIRTUAL FILE SYSTEMHow ASP.NET Developers can leverage SharePoint
- 17. WHY USE IT?Web PartsWeb Part ZonesCustomisationPersonalisation
- 18. dEMO: WEB PARTSHow ASP.NET Developers can leverage SharePoint
- 19. WHY USE IT?DeploymentDeploys to all server roles in FarmDeploys all dependent filesWeb.config changes
- 20. dEMO: SOLUTION PACKAGESHow ASP.NET Developers can leverage SharePoint
- 21. WHY USE IT?MOSSWeb Content ManagementDocuments ManagementRecords ManagementBusiness Data CatalogueExcel ServicesInfoPath Form ServicesEnterprise SearchMy Sites
- 22. MISCONCEPTIONS OF SHAREPOINTHow ASP.NET Developers can leverage SharePoint
- 23. MISCONCEPTIONS OF SHAREPOINTDebugging is hardDeployment is badSkinning is hardGAC onlyIt's expensiveNo client side validationNo support for AJAX and 3.5Hard to migrate existing ASP.NET sites
- 24. dEMO: EXISTING ASP.NET SITESHow ASP.NET Developers can leverage SharePoint
- 25. ISSUES AROUND LEVERAGING SHAREPOINTHow ASP.NET Developers can leverage SharePoint
- 26. ISSUES AROUND LEVERAGING SHAREPOINTServer developer environment Complex frameworkWSS has its limitsTroubleshooting Security errors toughCAML is hard to learn.NET Object Model is a COM wrapperRight and wrong way to build Test & Production(Accessibility)
- 27. LIMITATIONS OF OUT OF THE BOX AREASHow ASP.NET Developers can leverage SharePoint
- 28. LIMITATIONS OF OUT OF THE BOX AREASWCMNot intuitive enough for AuthorsIt all can be done...but needs more effortRemember MCMS?www.WesternAustralia.com.au web castsWikisBlogsRecords ManagementFor more see my ‘Leveraging the SharePoint Platform’ series
- 29. WHEN TO STICK WITH ASP.NETHow ASP.NET Developers can leverage SharePoint
- 30. WHY TO STICK WITH ASP.NETClient environment developmentConfiguring server is straight forwardLess Complexity (Junior Devs)ASP.NET 4.0 comingLarger communityData Access LayerFull control over user interfaceLots of other WCMS products out there
- 31. SummaryHow ASP.NET Developers can leverage SharePoint
- 32. SUMMARYIt’s an extension of what you already knowSharePoint is not going awayMicrosoft Server Products moving to PlatformMicrosoft see it as a Development PlatformDo it if you’re going to need the featuresDon’t do it if you’re not going to utilise itCan always be ported in later
Editor's Notes
- #13: Create a new web app in Central AdminCreate a new Site CollectionShow inetpub directory, IIS application pool and IIS web appCan create these programmatically
- #15: Show 12 HiveShow features and how they are activated in sites for component based development
- #17: Show SharePoint Manager and SharePoint DesignerShow Creating ListsShow Creating FieldsShow VersioningShow Views
- #19: Demo adding a web part to an existing pageWeb Part ZonesShow Web Part PropertiesAudiences
- #21: Demonstrate creating a Visual Studio WSPBuilder Project with a Feature to deploy a Web Part
- #25: Deploying Master PageAdding User ControlsAdding ASP.NET AJAXWeb.Config changes
- #27: Server developer environment Need to run Visual Studio with elevated permissionsArchitecture requires knowledge of Active Directory, DNSComplex frameworkMSDN – poor – autogen’d documentation and unstructured contentSharePointDevWiki.com Too many ways to do the same thingWSS has its limitsMOSS Internet Connector is $$$Troubleshooting Security errors toughCAML is hard to learn.NET Object Model is a COM wrapperRight and wrong way to build Test & Production(Accessibility)