Outsource Your Microsoft SharePoint 2013 Requirements to the Experts
  Home Why Us Services Case Studies Contact Us  
  SharePoint 2013, Microsoft Office SharePoint Server (MOSS 2007) and Windows SharePoint Services (WSS 3.0) Expert Group
SharePoint Services
Excel Reporting Service
Business Intelligence
Enterprise Content Management
Business Process and Forms
SharePoint Collaboration
Custom SharePoint Development
SharePoint Search
SharePoint Consulting
MOSS Portal Development
SharePoint Workflow Integration
SharePoint Personalization
Web Part Development
SharePoint White Paper
SharePoint Branding
 
 
 
Home > Services > SharePoint Sites Development and Management
 
SharePoint Sites Development and Management (Administration)
 
Microsoft Office SharePoint Server provides a complete model to create as well as manage web sites which can utilize the most important information of the organization when it is needed by any user. First you create a site using SharePoint and then you can customize it depending upon your needs.
 
SharePoint WSS
 
SharePoint 2013, is a great development platform that allows customizations via supported extensibility models. There are two ways to add custom functionality to SharePoint 2013: SharePoint Solutions and SharePoint Apps.
 
SharePoint Solutions
SharePoint Solutions can be developed using Visual Studio 2012, which includes a number of supported templates. They can integrate with external applications using Business Connectivity Services (BCS), Web Services, or a custom Service Application.

There are two types of SharePoint Solutions: Farm Solutions and Sandboxed Solutions.

 
Farm Solutions,
first introduced in MOSS 2007, are fully-trusted and have access to the full farm. It must be deployed by a Farm Administrator and run in the main SharePoint worker process. Customizations added via Farm Solutions are available to the entire farm.

Farm solutions are better choice for a wide array of custom features, such as branding solutions and administration tools and same time it can deployable in individual Web Applications, Site Collections, and Sites.

 
Sandboxed Solutions,
first introduced in SharePoint 2010, are partially trusted, and can only access a subset of the server-side Calls. Sandboxed Solutions can be deployed (uploaded) by a Site Collection Owner or Administrator Customizations added via Sandboxed Solutions are available to the entire Site Collection, to which they are deployed, making them a great choice for an array of features, such as custom workflows or site/list/library templates. Sandboxed Solutions are still available in SharePoint 2013 but they are deprecated with SharePoint Apps.
 
SharePoint Apps
This is a brand new extensibility model introduced in SharePoint 2013 that addresses some of the inherent challenges with SharePoint Solutions. The biggest difference between apps and solutions is that apps run completely outside of the SharePoint server, meaning their custom code is executed either in the context of the client browser or on other servers not running SharePoint (i.e., any Web server hosted on premise or in the Cloud). Therefore, this model provides the highest level of app isolation. However, as a result, apps cannot natively interact with other apps. SharePoint Apps are generally scoped to individual Sites or a special Site called the App Catalog, which allows for other Sites to connect and consume the app.

SharePoint Apps can be developed using Visual Studio 2012, which includes a fully supported app template. SharePoint Apps can leverage any of the industry Web standards such as HTML5 and CSS3, JavaScript and jQuery (or any other frameworks/libraries), JSON, REST, OData, and OAuth.

 
There are three types of SharePoint Apps:
  • SharePoint-Hosted Apps
  • Provider-Hosted Apps,
  • Azure Auto-Hosted Apps.
 
SharePoint-Hosted Apps are manifested entirely within SharePoint server and generally have no external dependencies. Their custom code is implemented by leveraging Client-Side Object Model (CSOM) or REST API, and is executed within the context of a browser. SharePoint-Hosted Apps can access libraries and lists to store content.
 
Provider-Hosted Apps may have SharePoint components, similar to SharePoint-Hosted Apps, but the main business logic and data storage are manifested in an external infrastructure, such as an external Web server or in the Cloud. Provider-Hosted Apps can also be developed using any other non-Microsoft tools and technologies because the business logic and data storage are provisioned by the external infrastructure.
 
Azure Auto-Hosted Apps are somewhat similar to the Provider-Hosted Apps in that their main business logic and data storage are manifested in an external infrastructure. However, the Azure Auto-Hosted App package additionally contains the Website and database that is deployed and run outside of SharePoint. Here SharePoint handles automatic provisioning of the Azure SQL Database and Azure-Hosted Website in an existing Azure account setup in the farm.
 
SharePoint Solutions have inherent issues that stem from their complexity and that they run directly on the SharePoint server. Farm Solutions are the root cause of most SharePoint outages and errors; they are cumbersome to deploy and not suitable for hosted environments. Sandboxed Solutions have access to limited server-side API, but still require knowledge and experience with the server-side API.
 
SharePoint Apps are now the preferred method for developing SharePoint customizations. They have the following advantages over SharePoint Solutions:
  • Stability: Since SharePoint Apps never run on the SharePoint server, this greatly increases the stability and performance of the farm. It makes it easier to upgrade to the next version of SharePoint since testing platform independent Apps is easier and faster than testing Solutions.
  • Security: SharePoint Apps can leverage the newly added support for OAuth 2.0, which provides an easy way to manage their permissions. Developers can specify which permissions the app needs in order to function. The end-user installing the app is then prompted to accept the permission request the app needs to function.
  • Reusability: Apps can be packaged, reused, and sold via a Corporate or Public Marketplace, which makes it easy for end-users to acquire new apps. The same APPs will work in both on-premise and Cloud environments.
   
Home | Why Us | Services | Case Studies | Inquiry | Contact Us | Site Map