BEGINNING sharepoint& #174; Development 2nd Chapter--sharepoint App Model Overview SharePoint app model

BEGINNING SHAREPOINT? Development 2nd Chapter--sharepoint App Model Overview SharePoint app model you can install SharePoint in two basic ways.

For SharePoint 2010, you can install the full version number of SharePoint Server, and perform all the assets and content in the on-premises environment.

The optional is. You can provide an instance of Office 365 (O365) and then take advantage of SharePoint Online (or a SharePoint Cloud support version number). You see some examples of SharePoint online in the first chapter, and you'll see a lot of other things in this chapter.

Regardless of how you deploy SharePoint instances, the new app model for SharePoint is available for the on-premises SharePoint version number (SharePoint Server) and the Cloud Support version number (O365).
Although you can manually create a SharePoint 2013 site collection. And be configured and branded to meet business needs. But this book is about development.

One of the key areas of improvement in SharePoint 2013 is the new app model. Broadly speaking. By creating and deploying SharePoint apps or Office apps, you're applying a new cloud model.
Office Apps Office apps are derivative products of Office 2013 applications. Use managed code methods to build documents and mail apps (think of Excel, Word, and Outlook components). These apps enable you to build lightweight apps with HTML, CSS, or JavaScript, and integrate with cloud-based apps.

The cool thing here is that you can use the rich JavaScript object model to integrate with a document or mail item section.

Office apps include Web pages plus XML-based configuration file manifest files that are configured with items such as links to external sites, permissions, and so on. You can consider Office apps as web apps.
Although Office apps primarily target office. You can integrate them with Office365, documents, and mail items-all of which may be integrated with SharePoint in some way. Shows an example of an office app. It integrates with mail to display data from a Windows Azure SQL database in a mail item: Related requests from Chris Johnson.

SharePoint Apps assumes you are familiar with the SP. The ability to be an SP app is an evolution of SP solution (WSP). But here the SP app uses the extended name. App.
The SP app is a move to a more focused cloud development model--the code is not on the same server as the SP. This is the result of code migration to the cloud. It is also the need to build platforms that support smoother updates. The code and SP are less tightly deployed to the cloud, easing some of the typical server-side code problems (such as performance and site load issues, when the code is not well written, deployed, or tested). Show the SP APP, integrated with Windows Azure data-in fact, the same data used in the app.

Mentioned before. When you build the SP app, you are building one. App files.

As a matter of fact. The app file is a package similar to a CAB file. There are many important files in the. App package, which are mainly composed of configuration files and libraries. For example, a. app file created when you build and publish the SP app is shown, and you'll do it later. Suppose you change. App extension is called. zip and you'll see that the. app file includes many files and a ZIP file.

These zip files represent the Web page portion of the SP application, and the XML file represents the more specific configuration information for the app.

One of the XML configuration files you'll see in SP Apps and Office apps is the Appmanifest.xml file.

You'll find key elements such as app metadata, app permissions and permissions, Web apps GUIDs, and more. The following code slice shows a simple example of a appmanifest.xml file.

<?
XML version= "1.0" encoding= "Utf-8"?> <app xmlns= "Http://schemas.microsoft.com/sharepoint/2012/app/manifest" Name= "Autohostedemployeelist" productid= "{125f9ba3-5efc-414a-ac53-023919ac2142}" version= "1.0.0.0" sharepointminversion= "15.0.0.0" > <Properties> <Title>AutohostedEmployeeList</Title> < Startpage>~remoteappurl/pages/default.aspx? {Standardtokens} </StartPage> </Properties> <AppPrincipal> <AutoDeployedWebApplication/> </AppPrincipal> <AppPrerequisites> <appprerequisite type= "autoprovisioning" id= "Remotewebhost"/> </AppPrerequisites> <apppermissionrequests><apppermissionrequest scope= "http://sharepoint/content /sitecollection/web "right=" Write "/></apppermissionrequests></app>

Note: You can change the XML directly by using the VS2012 IDE (visual designer) or by right-clicking the file selector to view the code.

BEGINNING sharepoint& #174 Development 2nd Chapter--sharepoint App Model Overview SHAREPOINT app model