Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à How ASP.NET Developers can leverage SharePoint
Similaire à How ASP.NET Developers can leverage SharePoint (20)
Dernier
Dernier (20)
How ASP.NET Developers can leverage SharePoint
- 1. How ASP.NET Developers can leverage SharePoint Jeremy Thake Senior Consultant, Readify http://bit.ly/JTHAKERATE
- 2. Agenda Introduction How ASP.NET Developers can leverage it Why Use It? Misconceptions The issues around leveraging it Limitations of OOTB areas When to stick with ASP.NET Summary
- 3. INTRODUCTIon How ASP.NET Developers can leverage SharePoint
- 4. KEY DRIVERS FOR ASP.NET DEVELOPERS Fast Compiling IDE Performance Can handle Complex Scenarios Easy to debug Easy to learn Simple API Lots of learning resources
- 5. INTRODUCTION Awareness People hate it “It’s not open source” Frameworks Over engineered Dependencies Developers like to write it themselves Feel out of control
- 6. WHAT IS IT
- 7. HOW YOU CAN LEVERAGE IT How ASP.NET Developers can leverage SharePoint
- 8. WHAT YOU NEED Windows Server Visual Studio 2005/8 SQL 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 MOSS Common User Interface Common Framework Common Data Layer Common Disaster Recovery
- 11. WHY USE IT? Leverages already existing knowledge of ASP.NET IIS Web Applications and Application Pools Web.Config Visual Studio IDE (C#/VB.NET) Master Pages Page Layouts Web Parts User Controls Site Themes XHTML/JavaScript/CSS
- 12. dEMO: CREATING WEB APPS How ASP.NET Developers can leverage SharePoint
- 13. WHY USE IT? Framework Security Component based Logging Persistence Architecture Extension File storage Audiences (MOSS)
- 14. dEMO: FEATURES How ASP.NET Developers can leverage SharePoint
- 15. WHY USE IT? SharePoint Lists CRUD Metadata Versioning Item Security Views Event Handlers Workflow Search Recycle Bin Custom Field Controls Incoming email
- 16. dEMO: VIRTUAL FILE SYSTEM How ASP.NET Developers can leverage SharePoint
- 17. WHY USE IT? Web Parts Web Part Zones Customisation Personalisation
- 18. dEMO: WEB PARTS How ASP.NET Developers can leverage SharePoint
- 19. WHY USE IT? Deployment Deploys to all server roles in Farm Deploys all dependent files Web.config changes
- 20. dEMO: SOLUTION PACKAGES How ASP.NET Developers can leverage SharePoint
- 21. WHY USE IT? MOSS Web Content Management Documents Management Records Management Business Data Catalogue Excel Services InfoPath Form Services Enterprise Search My Sites
- 22. MISCONCEPTIONS OF SHAREPOINT How ASP.NET Developers can leverage SharePoint
- 23. MISCONCEPTIONS OF SHAREPOINT Debugging is hard Deployment is bad Skinning is hard GAC only It's expensive No client side validation No support for AJAX and 3.5 Hard to migrate existing ASP.NET sites
- 24. dEMO: EXISTING ASP.NET SITES How ASP.NET Developers can leverage SharePoint
- 25. ISSUES AROUND LEVERAGING SHAREPOINT How ASP.NET Developers can leverage SharePoint
- 26. ISSUES AROUND LEVERAGING SHAREPOINT Server developer environment Complex framework WSS has its limits Troubleshooting Security errors tough CAML is hard to learn .NET Object Model is a COM wrapper Right and wrong way to build Test & Production (Accessibility)
- 27. LIMITATIONS OF OUT OF THE BOX AREAS How ASP.NET Developers can leverage SharePoint
- 28. LIMITATIONS OF OUT OF THE BOX AREAS WCM Not intuitive enough for Authors It all can be done...but needs more effort Remember MCMS? www.WesternAustralia.com.au web casts Wikis Blogs Records Management For more see my ‘Leveraging the SharePoint Platform’ series
- 29. WHEN TO STICK WITH ASP.NET How ASP.NET Developers can leverage SharePoint
- 30. WHY TO STICK WITH ASP.NET Client environment development Configuring server is straight forward Less Complexity (Junior Devs) ASP.NET 4.0 coming Larger community Data Access Layer Full control over user interface Lots of other WCMS products out there
- 31. Summary How ASP.NET Developers can leverage SharePoint
- 32. SUMMARY It’s an extension of what you already know SharePoint is not going away Microsoft Server Products moving to Platform Microsoft see it as a Development Platform Do it if you’re going to need the features Don’t do it if you’re not going to utilise it Can always be ported in later
- 33. http://bit.ly/JTHAKERATE http://wss.made4the.net@jthake http://www.SharePointDevWiki.com @SPDevWiki http://www.sharepointusers.org/Perth/ http://www.readify.net/rdn/
Notes de l'éditeur
- Create a new web app in Central AdminCreate a new Site CollectionShow inetpub directory, IIS application pool and IIS web appCan create these programmatically
- Show 12 HiveShow features and how they are activated in sites for component based development
- Show SharePoint Manager and SharePoint DesignerShow Creating ListsShow Creating FieldsShow VersioningShow Views
- Demo adding a web part to an existing pageWeb Part ZonesShow Web Part PropertiesAudiences
- Demonstrate creating a Visual Studio WSPBuilder Project with a Feature to deploy a Web Part
- Deploying Master PageAdding User ControlsAdding ASP.NET AJAXWeb.Config changes
- 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)