Tag Archives: external

Microsoft Sharepoint Development Creating External Lists

Microsoft Sharepoint Development Creating External Lists

One of the most acknowledged features of Microsoft SharePoint for Microsoft SharePoint development is external lists which have converted the MOSS 2007 Business Data Catalog (BDC) into Business Connectivity Services (BCS) in SharePoint 2010. It can be created independent of the SharePoint server as it is already included in Microsoft foundation. External lists though look like regular lists to an end user actually spread to external systems such as web services and databases.

Developers who have worked with BDC earlier know very well what a trouble it is to create external list. Heavy data XML files which contained the application definition were to be forged. This was a very massive task and developers often depended on external tools to make the task easier for them. The latest version of Microsoft SharePoint development that is SharePoint 2010 has made creating external lists really very simple, speedy and fast. A SharePoint developer can expose them under SharePoint 2010 in just 10 minutes if the database table is ready.

To create external lists for the customer external content type based on the customers table in Northwind database using Microsoft SharePoint development you will have to first run Business Data Connectivity Service Application. Ensure that it is running perfectly by going to central administration panel and click on manage service applications. Apart from this you will need external content type and Microsoft SharePoint Designer 2010 or the browser.

Server running SharePoint server should be equipped with Microsoft SQL Server 2005 or later, Northwind SQL Server 2000 database and customer external content type for creating external lists using Microsoft SharePoint development practices. To begin with move to SDK Samples SharePoint site from the Microsoft SharePoint Designer 2010. Click View All Site Content from the site’s actions menu on the left. Click the create button and then click external list from the custom lists section. Here we will create a new external list by entering a new name and a small description for the list on a new page.

Type the name of the external content in the text box if you know the name of the content type in the data source configuration section or else use the picker to help you pick the right name. It lists all different external content types denoted in the metadata store of the site’s service application’s Business Data Connectivity (BDC) service. After selecting the type in Microsoft SharePoint development click external content type picker.

Now SharePoint developer can move to the new list in the SharePoint site to view and edit items in the list. It is not mandatory to work online you can easily move the list offline in SharePoint Workspace and Microsoft Outlook.

Similarly external lists for customers can be created using Microsoft SharePoint development. The beginning process remains the same as mentioned above with the only difference that you need to select customer external content type as the data source. Click the create lists and forms button as shown in the figure to open the create list and form for customer dialog box. Name the new external list as NWCustomers List, SharePoint designer will then generate external list.

http://www.sooperarticles.com/technology-articles/software-articles/microsoft-sharepoint-development-creating-external-lists-176066.html

Understanding Sharepoint 2013 Apps Deployment Models

Understanding Sharepoint 2013 Apps Deployment Models

SharePoint 2013 is one of the best iterations of Microsoft’s document management and collaboration platform. SharePoint is moving to the cloud as per the market trends, and this means that SharePoint is now opting for a software-as-a-service model. The approach is hailed by analysts as a future-oriented move from Microsoft and will work for the benefit of the clients.

SharePoint is supposed to be much more useful when it is completely customized and aligned to the operations within an organization and strategies within a business. SharePoint’s functionality is certainly useful, but to realize the full potential, one needs to have a custom SharePoint setup as their intranet solution. It is a problem if it is hosted since custom code runs in shared environments and if bad code is entered, it has the ability to bring down a server to its knees and affect the existing customers harshly.

SharePoint 2013 now allows customers to build own SP-based solutions without interfering with the hosted model. The new model is called the SharePoint App Model, which does not have server-side code.

There are three deployment models for SharePoint 2013 Apps which include SP hosted. Self-Hosted, Azure Web Application. A SharePoint-Hosted App is based on static files that reside directly in the SharePoint instance. When you add an application, SharePoint deploys files in the App to a new domain where the App lives. The users are redirected to a page in the App domain from which they have the ability to use the App. No server-side code is allowed absolutely in this model.

A Self-Hosted App on the other hand is an application where the app files exist on an external server outside of SharePoint. When the application is accessed, they are redirected to the external server page where the application resides. One can run server-side code through this model, but on an external server. One can’t run custom code on the SharePoint server. The external server does not need to be based on Windows because the redirections are made to a web page, which can run on any operating system and application servers.

The model also gives the user complete control of upgrades. One can deploy updates and have them applied immediately to the clients. When deploying under different models, users have to perform actions to upgrade since there is no access to the server to the hosted app.

An Automatically-Provisioned Azure App is different from other deployment models since it is designed to run only from Microsoft’s hosted SharePoint environment so its clients are mostly SharePoint online customers. The other two App model options can be seen in hosted SharePoint environment as well as a part of the corporate installation.

An Automatically-Provisioned Azure App is designed to be deployed to Azure and hence can run custom code. One can avail all capabilities and server-side code without having to shell out money!

As a Microsoft SharePoint Application development vendor, one needs to make the choice. If one opts for a SharePoint-Hosted App, server side code cannot be run, which also means that you do not have to shell money for the server to host your app.

http://www.sooperarticles.com/technology-articles/programming-articles/understanding-sharepoint-2013-apps-deployment-models-1358726.html