Tab: 2013 SharePoint
Beginning SharePoint? 2013 development 1st chapter -- SharePoint 2013 describes how to handle developers' needs Sharepoint is essentially a platform. You must understand the platform functions to know how SharePoint can help you (developers ). When you explore and understand the functional scope of the platform, you will see interesting and attractive opportunities for developers. Let's look at a real example. As you know, a business production platform means that end users can be more collaborative and productive in their daily work and life-of course SharePoint can. It can be immediately used by end users as applications. For example, a HR department may use SharePoint management employee review, or the sales team uses it to manage the monthly sales prediction dashboard for Bi. In all these cases, Sharepoint first represents the end-user collaboration platform, and second represents the basis for enhanced or expanded development by skilled developers. Therefore, when your sales manager comes to you (developers), you need to design a Sharepoint website set and integrate daily sales data from the SAP system, then draw a market with high potential in the map on the SharePoint site-so that the sales staff can see the current sales path and opportunity area-you will want to know how such apps in SharePoint will be displayed .. We can look at this task from two perspectives:
- End user. They want a website where they can open, manage sales documents and tables, filter/fill in data, and then quickly view the target on the map. They want easy-to-use and controllable Apps;
- Developer. To achieve an easy-to-use and intuitive experience and efficient management.
As a developer, you want to maintain two points of view during task execution. In this process, you may need to consider the built-in functions for each task application solution, such as the document library and list, and core services, functions, and the platform's built-in APIs, to bring you to the next level (from the development perspective ). You can also integrate third-party or custom cloud-based services to improve the development experience. For this special example (with your sales manager), you may need to use the business connection service (BCS) (which is a series of SharePoint built-in services that allow you to connect to the business line system) and Excel services, in this way, you can create a pivot table for the sales staff. The final result of BCS is a dynamically generated list app and document library app that contains sales data (you can save the electronic form ). Therefore, you need to create two types of apps-document library (using Excel services) and external list app to load external lob data. Then you can integrate HTML or Javascript-based Apps (using cloud deployment services) to create a bing map, and then map the Green Map to represent the high-potential areas, red represents the low-potential or saturated market. This app is the third, but later it uses the service you inserted (such as Bing Maps service) and your custom service (with logic to create a graph based on certain business rules or information ). You can develop and deploy these three apps on the website of an existing team or a new custom site. In this example, you can use Sharepoint to create interesting experiences based on your audience requirements. You should always remember these options when designing and building your own SharePoint experience. Expand SharePoint 2013 although SharePoint represents a series of connected apps and features, it still has many opportunities for developers to expand the rich end user experience at multiple levels. When you consider SharePoint in an enterprise developer environment, this experience is obviously important. However, when independent software vendors ISVs consider the custom experience they want to deploy to customers, it is important to have a reliable platform that can be deployed and used to customize their SharePoint solution. Moreover, they demand a place for profit; that is, an app store not only provides a place for deployment and advertising, but also provides a place for product or directory integration. Their businesses are platform-based stability, predictability, accessibility, and discoverability. So what does SharePoint 2013 mean? As more extensive cloud models enter and integrate, expanding and building on SharePoint means that more web development partners, customers, and ISVs can join the SharePoint phenomenon. Some forms of participation include: creating lightweight apps for Sharepoint (such as HTML and JavaScript Apps) use the new cloud app model to build technologies based on Windows azure apps or using a wider range of web standards and technologies. To better understand this scalability, you can search for the paper "Now is the time to determine SharePoint's place in your application development strategy", John R. rymer and rob koplowitz reinforce the SharePoint 2013 model (composed of different layers ). The two authors propose that SharePoint have an application layer (end users are integrated with out-of-the-box collaboration and production applications ); A custom layer (rights users and developers can start to customize the SharePoint experience for end users) and a layer-3 Application Development layer. The Application Opening layer is an interesting layer for developers. At this layer, you will mostly find solution developers who build and deploy applications or business solutions (or integrate them through existing SharePoint components such as Web components or event receivers. How the application development layer evolved is also an interesting part. Illustrates how SharePoint 2013 evolved from an early application development model.
Displays SharePoint 2007 running custom code or services from IIS and other servers. Most of the custom code runs in the application pool using IIS resources. In 2010, Sharepoint supports running on IIS (or other servers), and introduces the sandbox solution and client object model csom
Beginning SharePoint®2013 development 1st chapter -- SharePoint 2013 describes how to handle developers' needs
