Developing a Microsoft SharePoint-based site is, according to marketing, simple and efficient. Efficiency is increased by giving the developer the option to easily add functionality to the site. One way to add functionality is through so called add-ins. An add-in extends the functionality of the site by running independent code on the client, cloud or a server outside the SharePoint farm. Add-ins can be added to the site through a web-based market or by creating new ones. The general question is if creation of new add-ins is worth the effort. This discussion can begin by investigating what implementation detail is reoccurring when developing this add-ins as well as what part of the process the most time is consuming. By attempting to create add-ins and the same time documenting the progress one can make conclusion regarding said questions. The result shows that the most recurring parts of development is how to manage the incoming data. It also seems as if the most time consuming part of add-in development is the research and construction of functionality that fetch data from the SharePoint-based site. Another part of the result is technical and contains information necessary to understand how the example add-ins are created. The add- ins that is presented in this paper concern document management which is a significant aspect of Microsoft SharePoint.
| Identifer | oai:union.ndltd.org:UPSALLA1/oai:DiVA.org:liu-136719 |
| Date | January 2017 |
| Creators | Jansson, Björn, Maghsoudi, Sebastian |
| Publisher | Linköpings universitet, Institutionen för datavetenskap, Linköpings universitet, Institutionen för datavetenskap |
| Source Sets | DiVA Archive at Upsalla University |
| Language | English |
| Detected Language | English |
| Type | Student thesis, info:eu-repo/semantics/bachelorThesis, text |
| Format | application/pdf |
| Rights | info:eu-repo/semantics/openAccess |
Page generated in 0.0022 seconds