Microsoft Sharepoint 2010 Sdk VERIFIED
The Microsoft SharePoint 2010 Software Development Kit (SDK) is available online and as a download. The SharePoint 2010 Reference: Software Development Kit download includes IntelliSense files and numerous additional code samples.
Microsoft Sharepoint 2010 Sdk
The SDK includes documentation and code samples for Microsoft SharePoint Foundation 2010 and for Microsoft SharePoint Server 2010, which builds upon the SharePoint Foundation 2010 infrastructure. The documentation includes detailed descriptions of the technologies that SharePoint Server 2010 and SharePoint Foundation 2010 provide for developers, reference documentation for the server and client object models, and step-by-step procedures for using and programming with these technologies and object models. This SDK also includes best practices and setup guidance that will help you get started with your own custom applications that build and extend upon the SharePoint Foundation 2010 and SharePoint Server 2010 platforms.
Microsoft SharePoint 2010 provides enterprise-scale capabilities to meet business-critical needs such as managing content and business processes. SharePoint Foundation 2010 is built on top of Internet Information Services (IIS) and the Microsoft ASP.NET Framework. For a description of this platform and its capabilities, see Conceptual Overview of SharePoint Foundation. SharePoint Server 2010 relies on SharePoint Foundation 2010 and provides a consistent framework for lists and libraries, site administration, and site customization. Any features that are available in SharePoint Foundation 2010 are also available in SharePoint Server 2010. For descriptions of extensible features areas and links to related documentation, see SharePoint Server 2010 General Reference.
To download the SharePoint 2010 SDK, see SharePoint 2010 Reference: Software Development Kit. For instructions on installing and using the SharePoint 2010 SDK, see Installing and Using the SharePoint 2010 SDK Download.
The SDK includes documentation and code samples for Microsoft SharePoint Foundation 2010 and for Microsoft SharePoint Server 2010, which builds upon the SharePoint Foundation 2010 infrastructure. This topic contains instructions about how to install and use the SharePoint 2010 SDK download.
By default, the SharePoint 2010 SDK installer installs documentation and samples for both SharePoint Foundation 2010 and SharePoint Server 2010. If you are developing only with SharePoint Foundation 2010, you may want to choose the setup option that installs only documentation and samples for SharePoint Foundation 2010.
If you are running Windows 7, You can access the Welcome Guide for the SharePoint 2010 SDK, which lists all of the code samples and provides quick links to important sections and topics, by clicking Start > All Programs > Microsoft SDKs > SharePoint 2010 SDK > Welcome Guide. If you have chosen to install only the samples and documentation for SharePoint Foundation 2010, click Start > All Programs > Microsoft SDKs > SharePoint Foundation 2010 SDK > Welcome Guide. From the Start menu, there are also direct links to the documentation for both SharePoint Foundation 2010 and SharePoint Server 2010.
You might want to create a directory for all SharePoint 2010 SDK samples. When uninstalling a previous version of the SharePoint 2010 SDK, the installer removes the original ZIP directories that contain the code samples. You may see leftover files, however, if you extract your samples to the Program Files directory. Additionally, you may encounter warnings or UAC prompts when you save the code sample ZIP directories to the Program Files directory. It is a best practice to install the code samples to the My Documents directory.
Currently the SharePoint 2010 SDK is available only in U.S. English. We are planning to make the SharePoint 2010 SDK available in additional languages, including Japanese, Simplified Chinese, French, Spanish, Russian, and Brazilian Portuguese.
The downloadable version of the SharePoint 2010 SDK is a compiled HTML Help (CHM) file (SP2010SDK.chm). This file is not accessible through the Microsoft Visual Studio 2010 context-sensitive Help system. If you want to be able to press the F1 button while writing and viewing your code in Visual Studio 2010, then you must use the online help option.
We continually expand and update the Microsoft SharePoint 2010 Software Development Kit (SDK), adding documentation for new and improved features of Microsoft SharePoint Server 2010 and responding to feedback from our customers. With this topic, you can quickly find the latest additions and changes to content and code samples.
You can obtain these and other code samples by downloading and installing the SharePoint 2010 Reference: Software Development Kit. In addition, see the SharePoint code samples available on Code Gallery.
Microsoft SharePoint 2010 provides three sets of APIs for developing extensions and custom solutions by using SharePoint capabilities: the server-side object model, the managed client object model, and Web services. Each API has advantages and limitations that you need to understand before you begin planning and developing custom solutions. For example, the server-side object model provides the most extensive set of options for developing customizations, but it can be used only on computers that are running a version of SharePoint 2010. The following sections describe the three sets of APIs and the contexts in which to use them.
The server-side object model provides the most extensive set of options for extending the capabilities of SharePoint 2010. It consists of every API that is documented in a class library in the SharePoint 2010 Class Libraries and Web Service References section of the Microsoft SharePoint 2010 Software Development Kit (SDK).
Any application that uses these APIs must be physically deployed on the server. See Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008 for guidance on and options for setting up a development environment. In terms of security, these APIs usually have a high level of access, but see Sandboxed Solutions for limitations that are related to sandboxed solutions. This set of APIs provides access to the largest number of features and capabilities. In Microsoft SharePoint Foundation 2010, many of the server-side APIs reside in the Microsoft.SharePoint assembly (Microsoft.SharePoint.dll); in Microsoft SharePoint Server 2010, many of these APIs reside in the Microsoft.Office.Server assembly (Microsoft.Office.Server.dll). However, you must look at the documentation for each type and member in each API to determine which assembly to reference.
The client object model allows you to integrate SharePoint 2010 capabilities into script that executes in the browser, code (no earlier than Microsoft .NET Framework 3.5) that executes in a .NET Framework managed application, or code that executes in a Microsoft Silverlight application. The APIs in the client object model are wrappers around a custom Web service that dispatches the calls to the server-side object model. They generally provide better performance than the SharePoint 2010 Web services because they batch requests and perform all operations asynchronously. They also feature design traits (such as object model hierarchy, object identity, data retrieval semantics, client context, infrastructural client objects, collections, and exception handling) that are familiar to SharePoint 2010 developers, and to Microsoft ASP.NET developers more generally. SharePoint 2010 provides an unmanaged ECMAScript (JavaScript, JScript) object model for script that executes in the browser. The unmanaged client object model is a good option for Web developers who are not familiar with ASP.NET development. The client object model focuses on the most relevant APIs for client-side development, and does not contain all the types and members that are represented in the server-side object model.
The client object model is designed for use in remote client-side solutions that run on computers where SharePoint 2010 is not installed. See SharePoint 2010 Client Object Model for more information about the client object model and how to use it. The types and members in these APIs are documented in Client Class Library (for code that executes in a .NET managed application or in a Microsoft Silverlight 2.0 application) and JavaScript Class Library (for code that executes in the browser).
The SharePoint 2010 Web services allow you to integrate SharePoint capabilities into code that runs remotely in client-side or server-side applications that run on computers where SharePoint 2010 has not been installed. SharePoint 2010 provides a limited set of REST interfaces for developers who are familiar with that standard. The Web services provide a fuller range of capabilities than the managed client object model, but they do not provide the same performance and design advantages, such as batching and exception handling. When you develop client-side applications, you should use the managed client object model whenever possible.
SharePoint 2010 Client object model SDK only has 2 dlls , it deos not have support for search. To access search functionality of SP 2010 from client application you have to rely on search.asmx service.
SharePoint 2010 goes well beyond basic content management into portal, search and collaboration technologies, and is attracting a large following as companies plan evolutions from their implementations of Microsoft Office SharePoint Server (MOSS) 2007. Over half the inquiries Gartner receives about ECM include discussion of SharePoint.
Nintex Forms 2010 provides a set of Representational State Transfer (REST) methods with which you can retrieve, publish, and delete forms in SharePoint 2010. However, SharePoint 2010 only implements Simple Object Access Protocol (SOAP) service operations, and so you must first invoke a SOAP service operation from SharePoint 2010 to obtain authentication before you can invoke the REST methods from Forms 2010. 041b061a72