SharePoint Framework, Sharepoint Add-ins, and farm solutions are all developed on the SharePoint development platform. To begin your development, familiarize yourself with SharePoint’s capabilities and features. 

Basic SharePoint concepts should be learned for development: 

In SharePoint, there are two forms of development 

1. Administrative Development: 

Learn the fundamentals of Admin Level Development: 

1. SharePoint Farms 

2. Web apps for SharePoint 

3. Collection of information from the web site 

4. Webpages 

5. Checklists 

6. Document repositories 

7. Processes 

1. SharePoint Farms: 

A SharePoint server farm is a collection of servers that work together to provide support for a SharePoint site. There are three kinds of servers in a SharePoint server farm: i) Web front-end servers, ii) application servers and iii) database (SQL) servers. 

2. Web apps for SharePoint: 

We build a Web Application using SharePoint Central Admin, which creates IIS sites, so SharePoint Web Applications are IIS sites that are controlled and generated by SharePoint Central Admin. 

Every Web Application will include at least one content database, but there is no hard limit to the number of databases that can be used. Therefore, you can technically have up to 500 content databases for a single web application.

To create a new Web Application through the stsadm command follow below:

Open SharePoint Central Admin > Select “Application management” > Select “Manage Web Application” > Select “New” on top ribbon > Complete the details e.g., port number, host header URL, etc. and click OK. 

Reference: http://itfreesupport.com/2015/05/what-is-a-web-application-in-sharepoint/ 

3. Collection of information from the website: 

The site is the foundation of SharePoint and serves as the beginning point for developers; without it, you can’t begin developing SharePoint. 

There are numerous website themes from which you can pick. The subsites share administration settings, navigation, and permissions, which may all be customized as needed for each subsite. 

Set up a Site Collection: 

When learning a new application like SharePoint, it’s a good idea to set up a space where you can practice without disrupting existing systems or users. 

Step 1 − To begin, go to https://portal.office.com/ and create a new site collection https://portal.office.com/ 

Step 2 − You will get the following page after selecting the admin icon. 

Click Add a site in the right panel.  

Step 3: In the left panel, click Resources > Sites. In the right panel, click Add a site in the right panel. 

Step 4 − The following page will open. Click on the OK after providing the necessary information. 

You can notice that the site collection has been added to the URL list in your admin center. The URL is the location of the site collection where the administrator can begin to manage and construct sites. 

Step 5 − Click on the link to view the specific details about that site collection. 

4. Site Collection: A site collection is made up of a top-level site and all sub-level sites. As shown in the diagram, it is the top level of organization for a SharePoint Server online application. The capacity of your server architecture determines how many site collections you can have in a single web application. 

Create a web page 

1. Click + Create site on the SharePoint start page. 

2. In the mind of the wizard: 

• Make a decision about whether you want to create a communication or a team site. 
• Enter the URL of the website (and, if desired, a description). 
• By clicking Edit Image from the pencil icon, you can edit a flow. You can change the group email address or website address if you want. 

5. Lists: 

A list is a grouping of information that you may distribute to members of your team and anyone to whom you’ve granted access. There are several pre-made list templates available that can be used as an excellent place to start when organizing list elements. List templates in Microsoft 365 have further information. 

1) To access the Create a list chooser, select + New list. 
In SharePoint, select + New > List.  

2) To access the Create a list chooser, select + New list. 

On the library settings page, click Edit current view to modify or add new views. 

3.Click Create after giving your list a name, an optional description, color, icon, and website to save it too.   

4. Select + New in the command bar once you’ve established a new list.    

5.Complete the column values for the new item form, and then click Save. 

Note: List columns with an asterisk (*) are required, so you can’t leave them blank. 

6. Document repositories: 

Document libraries are SharePoint Server collections of files that you can share with other site users. Document libraries are used to give the majority of document management functionalities. 

The primary menu can be found in the upper left of the document library page. 

A new folder, document, or link to something outside the document library can all be created here. 

Note: The list of document types will vary depending on your permissions and how your site was set up. 

On the library settings page, click Edit current view to modify or add new views. 

The menu at the upper left of the document library transforms to a list of actions you can take on the folder or file you have selected. 

7. Processes:  

In many situations, we want some action like an item being added or changed to initiate the flow. Send an email from a web component, for instance, by clicking a button. 

1) Go to Power Automate in Office 365 after opening it. 

2) From the menu on the left, choose Create. 

3) Select “Instant flow” from the drop-down menu. 

4) In the modal dialogue, specify the flow name (e.g., QuickMailSend)  

5) Select the trigger “When an HTTP request is received.” 

6) Press Create. 

7) Create the flow as shown below. 

8) We want to write an email that includes the email address, the subject, and the body. The format of our request body is as follows: 
 

{ 

    “emailaddress”:”[email protected]“, 

    “emailSubject”: “Hello”, 

    “emailBody”: “Hello from Power Automate flow” 

} 

9) Make the “When an HTTP request is received” activity more extensive. 

10) Click “Generate from sample” in step 10. 

11) Include the request body JSON schema mentioned above in the pop-up. 

12) Press “Done. 

13) The request body JSON schema will be generated. 

14) Click “+ New step”. 

15) Locate and include the action “Send an email.” 

17) Choose “Add new step.” 

18) Select the response action. 

19) Press Save. 

20) Write the HTTP POST URL down. 

2. Development at the Developer Level: 

1. Object model on the server: 

The server-side Object Model provides the most comprehensive set of options for expanding SharePoint 2010’s capabilities. It includes every API that is documented in a class library in the Microsoft SharePoint 2010 Software Development Kit’s Class Libraries and Web Service References section (SDK). 

2. Customer Object Model: 

You can incorporate SharePoint 2010 functionality into the script that runs in the browser, code (no earlier than Microsoft.NET Framework 3.5) that runs in a.NET Framework managed application, or code that runs in a Microsoft Silverlight application thanks to the client Object model. Because they batch requests and carry out all actions asynchronously, they typically offer superior speed to the SharePoint 2010 Web services. They also have design characteristics that SharePoint 2010 developers are accustomed to, such as object model hierarchy, object identification, data retrieval semantics, client context, infrastructural client objects, collections, and exception handling. 

3. The object model for JavaScript: 

A collection of classes and libraries make up the JavaScript Object Model (JSOM), which is the client object model for SharePoint Online. These classes and objects can be used to interact with SharePoint data. 

4. Rest API for SharePoint: 

Use the API index to seek several of the most frequently used types and objects that are implemented in the.NET client-side object model (CSOM), JavaScript object model (JSOM), and/or REST, as well as the.NET server object model. 

The most popular core APIs, which are often based on types from the.NET server implementation, are listed in this table.  

Conclusion: 

Microsoft’s SharePoint solution has shown itself to be highly useful in managing large amounts of documents in one location. It is a secure, effective, and convenient organizational management solution. Another simple method for gathering data and controlling workflow is the connection of SharePoint with other programs. 

The post Essential of SharePoint development foundation appeared first on Zehntech.