Best Practces To Follow For SharePoint Development

1. Best Practces To Follow For SharePoint Development

2. Why use SharePoint For Your Business? Most widely used Enterprise Content Management System that facilitates collaboraton and improves business process.  Helps the informaton to ow freely, efectvely and collaboratvely by having access to the informaton at any level thus improving the decision making regarding resources allocaton or utlizaton.  Helps to connect the employees with informaton and expertse.  Helps the employees to share the informaton within the enterprise while protectng any proprietary informaton.  But, these benefts are totally dependent on how properly the businesses implement SharePoint. 

3. How Poor Coding Afects SharePoint Applicatons SharePoint applicatons are ofen customized according to the client’s requirements. The customizatons and the codes used to build them can have a major in uence on the below given aspects of SharePoint development: Performance – Even one line of bad code can afect the speed of your applicaton.  Security – Poor coding introduces security aws that are hard to detect.  Maintainability - ‘Spaghet code' might fulfl your requirements, but makes it very hard to apply the changes.  Stability – Finding bugs become difcult with poor coding, which decreases stability and leads to more errors. 

4. Microsof SharePoint Development Best Practces Businesses need to follow certain SharePoint best practces to avail the beneft from this robust platorm. These are:  Choosing right SharePoint development patern  Understand methodologies and design  Implement regular code reviews

5. Choosing Right SharePoint Development Patern The developed SharePoint apps needs to be integrated with the current level of SharePoint implementaton, be it on-premise or cloud.  This narrows down the decision making process for choosing right SharePoint development patern.  Although many development paterns have evolved over tme, there is no preference on its usage with each one having their own pros and cons.  Given below are some of the SharePoint development paterns:   Full Trust Soluton or Farm Soluton  JavaScript Injecton  Sandboxed solutons  Add-Ins or Apps  SharePoint Frameworks

6. Full Trust Soluton or Farm Soluton This development patern was introduced with SharePoint 2003. Pros of Farm Soluton Cons of Farm Soluton     Server Side (Trusted) executon Model Web.confg needs to be updated to make changes. IIS resets with these changes  Uses the server API for the product  Brings down the whole farm in case of serious error  Works only in on-premise implementatons (except for private and non-Microsof hosted implementatons)  Covers the entre farm

7. JavaScript Injecton Cons of JavaScript Injecton Method  Pros of JavaScript Injecton method   Most untrusted development model as executon is done on client side  Client Side Executon model  Client Side API usage  As it is scoped to current SharePoint page only, the entre customizaton takes more tme.  Can be built with any development tool kit  Scoped specifcally to the current SharePoint page only  Manually deployed with no publicly shared or known automaton model for deployment

8. Sandboxed solutons This development patern made its debut with SharePoint 2010 to resolve IIS Reset Problem  Pros  Cons of Sandboxed Solutons   Server Side (Partally Trusted) executon model  Neither force the servers to reset nor they could bring down the farm in case of integraton issues  Don’t have complete access to SharePoint farms (But more than a SharePoint Page)  Easily afected when Microsof made any changes  More manageable than JavaScript Injecton & benefts from integraton techniques and DevOps paterns  Pure client side customizaton not possible without Javascript Injecton

9. Add-ins or Apps This development patern was introduced with SharePoint 2013 that not only resolves the IIS Reset Problem but also allows any kind of soluton to be a SharePoint Applicaton. Cons of add-ins or apps  Pros of Add-ins or Apps   Javascript Injecton is stll required in case of traditonal web development as the executon is done in an iFrame  Client or Server side executon models  Client Side API Available – Client Side Object Modeling(CSOM) and other techniques allow for an Add-in to appear and behave very much like a natve SharePoint feature  Executon is externalized from SharePoint as it runs within an iFrame  Scopes to a Site in the case of SharePoint Online

10. SharePoint Frameworks It is an open source initatve released to ease deployment and change management Overcomes the limitaton of apps in regards to traditonal web development Pros  Cons   Client side executon model  Client side Executon Model makes it less trusted  Executed and rendered in the context of the page  Limited compatbility with on premise version of SharePoint startng with 2016.  Responsive and Mobile Friendly  Scoped to the Site Collecton using a exible deployment model

11. Understand methodologies and design It is the most important SharePoint best practce   Model-View-View-Model Many design paterns available to build quality SharePoint App.  e. g. Model-View-View-Model (MVVM) – Best example of how code is seperated from user- interface.  Choosing the right design patern or methodologies also depends upon the developer's expertse  Image Credit: htps://msdn.microsof.com/en-us/library/f7983383..aspx Proper sofware design is the foundaton to SharePoint performance. 

12. Implement regular code reviews It is necessary to implement regular code reviews and it should be the part of the development schedule.  Benefts of regular code reviews:   Ensures tmely detecton and mitgaton of errors in SharePoint applicatons  Can be done via tools like over-the-shoulder or via pair programming.  Improves your SharePoint applicaton from functonal & technical viewpoints

13. To conclude It is always a good idea to invest more eforts in design, development and review of SharePoint applicatons to ensure that the quality of the code writen is not afected.  Following these SharePoint best practces will ensure a robust SharePoint soluton for the enterprises. 

14. Thank You