Developing applications for sharepoint 2010 download

Still using SharePoint ? Upgrade to the latest version and create a mobile, intelligent intranet with SharePoint in Microsoft Get the most up-to-date version of SharePoint for a mobile, intelligent intranet. Upgrade to Microsoft today. My Sites are personal SharePoint sites. Each user has their own and can set their own preferences.

With just a click, you can discover information and actionable expertise thanks to improved content management and connections with Yammer. Get a scalable solution without all the overhead, and enjoy best-in-class security and compliance in the cloud. Stay more connected and productive with the SharePoint mobile apps. From simple, repetitive tasks to complex operational workflows, create rich digital experiences with forms, workflows and custom apps.

Android is a trademark of Google Inc. Before you can use the WCF service in SharePoint, however, there is another configuration step that is required. If you open the WCF service project, you'll see a web. WCF provides more granular and flexible control over your Web service settings, and you can use the web. To enable the service in SharePoint, you must copy and paste the Service Model settings in your web. This way, when SharePoint uses the endpoint URL, it understands the bindings and other properties defined in the config file it needs to use to properly handle the WCF service.

To find the specific elements that you need to copy, double-click the web. You can typically find the SharePoint web. The following code snippet shows the copied system. With the service deployed and SharePoint's web. When the service page loads, navigate to Service1. When the endpoint is loaded into the Service Reference dialog box, provide a name for the service and then click Add. Right-click the main Web part class file and then click View Code. Add the following bolded code to the main Web part class file.

After the Web part successfully builds, navigate to SharePoint and use an existing page or create a new Web part page, and then click Add a new Web part.

Select the Custom category, and add the new Web part you just created. The result should look similar to Figure 8. In much the same way that you created an ASP. NET Web service and then consumed it in an application, you walked through a similar process here using a custom WCF service.

However, there were some differences this time, even though you used the same database in your service code. First, your service code included the capability to add a record this time, as opposed to just retrieving data addSalesRecord.

In this method, you passed a number of parameters that you would eventually insert as a record. To do this, you created a new object, and then, using the database data context, you added an instance of the object to the database and saved the changes by calling the SaveChanges method.

Second, you added some configuration information to the SharePoint web. While this does make for an extra step in the development and deployment process, it does provide more granular control over the security and bindings for your services — and is very much typical of a WCF service.

However, remember that what you need is typically created in your web. In this case, implementing the service was fairly straightforward and only required that you call the addSalesRecord method and pass in a number of variables — which the user entered into the textboxes. The way in which you would deploy to the SharePoint root would be as follows:. Add a. You can review the project to see how it is structured, as well as the way in which a client application calls the WCF service.

You can build many more interesting and complex applications using WCF, so you should explore it more as you sharpen your SharePoint development skills. What this functionality provides to the developer is a way to interact with SharePoint data in a strongly typed way. They also provide a way to interact with other types of data in SharePoint, such as Excel data. For the following example, create an Excel spreadsheet, add some data to a workbook as shown in Figure 9 , and create a named range called Sales.

Next, create a chart from the named range by selecting all of the data in the table, clicking Insert , then Chart , and then selecting the Bar Chart to add the chart into the workbook.

Note that the chart is called Chart 1 by default. After you create the workbook, save and upload the spreadsheet into SharePoint — for example, into the Shared Documents document library with the name RestExample. REST is a lightweight set of protocols that you can use to interact with data in various ways, one of which is retrieving data from Excel.

Open your Internet browser and navigate to your SharePoint instance to ensure that you have connectivity to your server. In your Internet browser, you should now see something similar to Figure Because you created a named range in the spreadsheet, you can access the named range using theAtom feed. To do so, type the following URI into the Internet browser.

You should now see something similar to Figure 11, which shows the result of the Atom feed — the table that you made the named range in your Excel spreadsheet. Lastly, type the following URI into your Internet browser to expose the chart that you also created in the spreadsheet. There are also a number of supported REST return formats. This is what you did with the Sales named range in the walkthrough. Note that you could also return the data as an Atom feed as is indicated by the?

You saw one way to leverage the Listdata service in Chapter 5 where you developed a client application to talk to SharePoint lists , and here you should be thinking how you can develop applications that leverage the lightweight REST protocol to get and put data into SharePoint lists, or access data in Excel spreadsheets programmatically. A growing trend in software development is cloud computing.

Cloud computing is where code and data live in the cloud so that organizations can both consume and deploy services in an Internetbased data center for hosting. The business mechanics of cloud computing can make a lot of sense when thinking about things like hardware, upgrading, administration, and software maintenance. Cloud computing offsets these costs by moving the management and maintenance of applications to companies like Microsoft. One of the key Microsoft cloud offerings is the Windows Azure platform, which is a set of cloud capabilities that provides specific services to both those trying to host services in the cloud and those trying to develop and deploy services in the cloud.

Interestingly, the Azure platform is not limited to being consumed by cloud-only applications. You can integrate Azure services with on-premises applications as well.

In fact, the easy way to think about an Azure service is that it is very similar to any other service endpoint — except that it is deployed and hosted in the cloud. The demand for cloud computing is big, and, in the near term, you'll see many companies trying to integrate more with the Windows Azure platform. The question, then, is how does SharePoint integrate with the cloud? At present, SharePoint can integrate with Windows Azure services; again, it is just another endpoint.

Thus, you build and deploy a service in the cloud and, as long as you have connectivity to the service, you can integrate and run it with SharePoint. While this book mainly focuses on SharePoint on-premises that is, SharePoint Server , there is no reason why you cannot integrate Azurebased services with SharePoint does make for an extra step in the development and deployment process, Online for example, using sandboxed solutions as your point of integration when it is released later in Integrating SharePoint with Azure services or data primarily means two things at present.

The first is that you can integrate with services that are already hosted on Azure. Or, you can build your own Azure services or applications , deploy these services in the cloud, and then integrate these services with SharePoint. The Windows Azure platform provides a set of developer tools and a replicated developer environment where you can test any services you will deploy to the cloud.

For more information on how to get started using Windows Azure, see the Windows Azure Platform home page. An interesting data service that is built on Azure is a technology codenamed 'Dallas,' where companies are hosting large quantities of public data on Azure, and then, through a subscription model, you can build applications that leverage that data in some capacity.

While the technology is currently limited, in the future it is sure to grow in use and popularity, because the data will grow to include census, crime, and news data — and other types of data that can prove interesting when mined and analyzed in different ways.

In this section, you'll see how you can integrate Dallas data hosted on Azure integrated with SharePoint. To complete the exercise that follows, you'll need to have a Live ID and a developer key to access the Dallas data and services. Click Home and follow the instructions to get your developer key sent to you via email. It's a very simple process and will only take you a couple of minutes.

After you have your developer key, click Catalog , and then subscribe to one or more of the data catalogs. When you subscribe to a catalog, it is then added to your Subscriptions. For this walkthrough, use the infogroup data catalog that is hosted on Azure. Code file AzureProject. Navigate to your Dallas Azure Catalog page and click the link, Click here to explore the dataset as shown in Figure Explore the catalog using the Web-based filters to get a better sense for what public data is returned from your filtering.

Add the Web part item-level template to the Empty SharePoint project. Right-click the project, click Add , and then choose Class. Call the class Customer and add the following bolded code to the class. In the main Web part class, add the following bolded code.

Where noted in the code, add your account key, unique user ID, and the link to the data catalog. After you add the code, click Build to build the project. After the project has successfully built, click Build and then choose Deploy Solution to deploy the Web part to SharePoint. Once the Web part has deployed, navigate to your SharePoint site and either create a new Web part page or use an existing one. Click Add a web part , and then navigate to the Custom category. Add your newly created Azure Web part.

The results should look similar to Figure This example opens up the opportunity for you to begin to code against Azure-based services that live in the cloud. However, you shouldn't think of these services as any different from other types of services. These are simply a different endpoint. In this walkthrough, rather than using the service proxies as you did in the ASP. The WebRequest object is a.

Using this class, the request was sent from the client application using a specific URI in this case, the Dallas data URL , and the response was handled by reading the response stream into an XDocument object. In the walkthrough, the bulk of the code was invoked when you clicked the button in the Web part btnGetAzureData. After making the request, a good portion of the code within the Click event constructed a query that could be used to get the specific information you wanted.

You can certainly optimize this code with LINQ to get a more concise query against the returned data set, and you would likely want to emit the HTML formatting using the HtmlTextWriter class, as you've seen throughout the book. In this case, you created a query that parsed all records from the response stream that were located in the city of Sooke, British Columbia. After you bound the returned data to the datagrid datagrdAzureData , you then disposed all of the objects associated with the WebRequest.

Service-based applications open up a vast amount of potential for building interesting applications that span heterogeneous systems. In this chapter, you saw the increased support for services of all kinds in SharePoint Specifically, you learned about native and custom ASP.

All of these provide you with different capabilities and levels of functionality that can extend out into the enterprise, or out into the wider cloud. As a beginning developer, your first option should always be to see if the service exists already before creating a custom service. SharePoint has a rich set of native Web services, and you'll find that these will often fit the bill.

However, if the functionality does not exist in the native SharePoint Web services, then custom services may be the option. New Releases. Desktop Enhancements. Networking Software. Trending from CNET. Download Now. Developer's Description By Microsoft. Developing Applications for SharePoint contains guidance documentation, detailed examples, and a reusable class library. These resources are designed to help solution developers and architects make the right decisions and follow proven practices when designing and developing applications for Microsoft SharePoint The guidance focuses on the building blocks that every developer needs to understand to become an effective SharePoint developer or architect.

The guide is provided as a Help. Eight reference implementations illustrate the core concepts covered in the guide. The reusable class library provides code to help developers build more manageable, flexible, and testable applications. Source code is provided for all reference implementations and for the reusable library. The reference implementations have automated setup scripts to configure the applications. Full Specifications.

What's new in version 3. Release June 30, Date Added April 5,