Home
About Us
Advertise
Printable version
The App Model moves SharePoint development in the right direction
By Brian Prigge
August 27, 2013 —
(Page 1 of 2)
In what is arguably the largest paradigm shift in the history of SharePoint development, Microsoft has made a strong push toward the App Model in SharePoint 2013. Unlike traditional farm solutions in prior versions of SharePoint, the App Model brings a level of code isolation not yet seen in the SharePoint world.
Simply, the App Model allows “bolt-on” functionality; this is opposed to previous generations that have a very “bolt-in” functionality. This model can be used for many of the same situations in which the farm-solutions model would have been employed. These solutions may include complex integrations with external systems, the need to perform complex business logic, and any other custom development needed for SharePoint.
Apps are broken down into three basic categories: SharePoint-hosted, auto-hosted and provider-hosted. In all of the models, you have the ability to deploy SharePoint artifacts such as Lists and Libraries, but there are significant differences among them.
SharePoint-hosted apps are run exclusively in SharePoint. They do not require any outside hosting for any portion of the app, but they are considerably limited. Given that the goal for the App Model was code isolation, there is no way to run server-side code in a SharePoint-hosted app. You are limited to HTML, CSS and JavaScript.
Auto-hosted and provider-hosted both allow server-side code, but in a different web application that is outside of SharePoint entirely. This is where things become a bit trickier. Auto-hosted apps will automatically provision a hosting environment for your server-side portion (known as the remote web), but they are only available in Office 365. It will also provision a new site for each instance of the app.
Provider-hosted apps are supported in both the Server version of SharePoint as well as in Office 365. The detriment here is that the hosting environment for the remote web is not automatically provisioned. You must actively provision the hosting environment and associate it with your app. The good news is that you can use a single remote web for multiple app instances. This ability eases the burden of sending updates to multiple instances by allowing you to update a single remote web across many instances.
Next Page
Pages
1
2
Share this link:
https://sptechweb.com/link/64046
Related Articles
Customizing SharePoint Online Using SharePoint Designer, Part 1
Once you get a handle on SharePoint Online, the question becomes: How can I modify it to suit my needs. First of two parts.
Kodak helps SPTechCon attendees better manage their most valuable documents using Microsoft SharePoint
Experts at the Kodak booth will help attendees optimize SharePoint and automate workflows that process valuable documents
RAMP unveils beta of RAMP for SharePoint Online at SPTechCon Boston
Solution leverages RAMP’s MediaCloud platform to provide secure, cloud-based video management within Microsoft
Add comment
Name*
Email*
Country
United States
Canada
Afghanistan
Albania
Algeria
American Samoa
Andorra
Angola
Anguilla
Antarctica
Antigua & Barbuda
Antilles, Netherlands
Arabia, Saudi
Argentina
Armenia
Aruba
Australia
Austria
Azerbaijan
Bahamas, The
Bahrain
Bangladesh
Barbados
Belarus
Belgium
Belize
Benin
Bermuda
Bhutan
Bolivia
Bosnia and Herzegovina
Botswana
Brazil
British Virgin Islands
Brunei Darussalam
Bulgaria
Burkina Faso
Burundi
Cambodia
Cameroon
Cape Verde
Cayman Islands
Central African Republic
Chad
Chile
China
Christmas Island
Cocos (Keeling) Islands
Colombia
Comoros
Congo
Cook Islands
Costa Rica
Cote D'Ivoire
Croatia
Cuba
Cyprus
Czech Republic
Denmark
Djibouti
Dominica
Dominican Republic
East Timor (Timor-Leste)
Ecuador
Egypt
El Salvador
Equatorial Guinea
Eritrea
Estonia
Ethiopia
Falkland Islands (Malvinas)
Faroe Islands
Fiji
Finland
France
French Guiana
French Polynesia
Gabon
Gambia, the
Georgia
Germany
Ghana
Gibraltar
Greece
Greenland
Grenada
Guadeloupe
Guam
Guatemala
Guernsey
Guinea
Guinea-Bissau
Guinea, Equatorial
Guyana
Haiti
Holland (see Netherlands)
Honduras
Hong Kong, (China)
Hungary
Iceland
India
Indonesia
Iran, Islamic Republic of
Iraq
Ireland
Israel
Italy
Jamaica
Japan
Jordan
Kazakhstan
Kenya
Kiribati
Korea (North)
Korea (South)
Kuwait
Kyrgyzstan
Laos
Latvia
Lebanon
Lesotho
Liberia
Libya
Liechtenstein
Lithuania
Luxembourg
Macao, (China)
Macedonia, TFYR
Madagascar
Malawi
Malaysia
Maldives
Mali
Malta
Marshall Islands
Martinique
Mauritania
Mauritius
Mayotte
Mexico
Micronesia, Federated States of
Moldova, Republic of
Monaco
Mongolia
Montenegro
Montserrat
Morocco
Mozambique
Myanmar
Namibia
Nauru
Nepal
Netherlands
Netherlands Antilles
New Caledonia
New Zealand
Nicaragua
Niger
Nigeria
Niue
Norfolk Island
Northern Mariana Islands
Norway
Oman
Pakistan
Palau
Palestinian Territory
Panama
Papua New Guinea
Paraguay
Peru
Philippines
Poland
Portugal
Puerto Rico
Qatar
Reunion
Romania
Russia (Russian Federation)
Rwanda
Saint Helena
Saint Kitts and Nevis
Saint Lucia
Saint Pierre and Miquelon
Saint Vincent and the Grenadines
Samoa
San Marino
Sao Tome and Principe
Saudi Arabia
Senegal
Serbia & Montenegro
Seychelles
Sierra Leone
Singapore
Slovakia
Slovenia
Solomon Islands
Somalia
South Africa
Spain
Sri Lanka
Sudan
Suriname
Swaziland
Sweden
Switzerland
Syrian Arab Republic
Taiwan
Tajikistan
Tanzania, United Republic of
Thailand
Timor-Leste (East Timor)
Togo
Tokelau
Tonga
Trinidad & Tobago
Tunisia
Turkey
Turkmenistan
Turks and Caicos Islands
Tuvalu
Uganda
Ukraine
United Arab Emirates
United Kingdom
Uruguay
Uzbekistan
Vanuatu
Vatican City State (Holy See)
Venezuela
VietNam
Virgin Islands, British
Virgin Islands, U.S.
Wallis and Futuna
Western Sahara
Yemen
Zambia
Zanzibar
Zimbabwe
[Not specified]
Compose