In MOSS 2007 we used to develop as “WSP”
solution packages. These WSP files are deployed on farm which contains custom
managed code, declarative scripts etc. Farm administrator used to deploy
solutions.
In SP2010 one more concept was introduced
called “Sandbox Solutions” which are uploaded in site collection gallery and
installed on site collection by site owner also.
Now in SP2013 we have new development
model “SharePoint Apps”, everything in SharePoint 2013 is app.
MOSS 2007
|
SP2010
|
SP2013
|
|
Farm Solution (.wsp)
|
Yes
|
Yes
|
Yes
|
Sandbox solution(.wsp)
|
No
|
Yes
|
Yes
|
SharePoint Apps
(.app)
|
No
|
No
|
Yes
|
We can use wsp in SharePoint 2013
whenever we want to use develop below components:
- Site definitions
- Delegate controls
- Custom themes
- Custom action groups
SharePoint app model is flexible and can
be deployed office store for apps, on premise farms and SharePoint online.
Below are few points for why to of SharePoint app model
·
Apps are
nothing but Safe SharePoint extensions
to Administrators.
·
Apps are
easy to search on online store and simple installation process which can be
done by SharePoint end users. (Site owners, members)
·
Apps
provide maximum flexibility in developing new versions.
·
It gives
option to use your other programming skills like html5, JQuery/JavaScript.
·
Apps help
in integrating cloud-based resources (windows azure) in smoother and more
flexible ways.
·
You can
use SharePoint cross-domain JavaScript library/OAuth to read SharePoint data.
·
Apps enable
your extension to have permissions that are distinct from the permissions of
the user who is running the app.
·
Apps help
in use of cross-platform standards, including REST API, OData and OAuth.
Using SharePoint Apps You can develop
below components
- Custom Web Parts
- Event and Feature Receivers
- Custom Field Types
- Application Pages
No comments:
Post a Comment