In this article,how we can use the Ajax Control Toolkit in Sharepoint 2010.using this sharepoint designer and Visuval studio.
1.Download the Ajax Control Toolkit from this url Click here.
2.Add Ajax Control Toolkit ScriptManager in your master page.Open the Master page in SharePoint Designer.
Culture=neutral, PublicKeyToken=28f01b0e84b6d53e"
Namespace="AjaxControlToolkit" TagPrefix="ajaxToolkit" %
- First register the Ajax Control Toolkit namespace in the masterpage file by putting the following line at the top of the file
Culture=neutral, PublicKeyToken=28f01b0e84b6d53e"
Namespace="AjaxControlToolkit" TagPrefix="ajaxToolkit" %
- Then remove the ScriptManager registration from the master page by removing the following line:
<asp:ScriptManager id="ScriptManager" runat="server" EnablePageMethods="false"
EnablePartialRendering="true" EnableScriptGlobalization="false"
EnableScriptLocalization="true"/>
- Finally Add the following line in place of the above line to register Ajax Control Toolkit
<ajaxToolkit:ToolkitScriptManager id="ScriptManager" runat="server" EnablePageMethods="false"
EnablePartialRendering="true" EnableScriptGlobalization="false" EnableScriptLocalization="true"/>
3.Register Ajax Control Toolkit namespaces in SharePoint package Designer
First open the Package designer in Visual Studio (Package usually exists under Package folder in Visual Studio). And then click the “Advanced” button in package designer window as shown in the image below. In that advanced tab you can add/edit assemblies to be registered safe as part of the deployment of the solution package. Click Add ==> “Add Existing Assembly”. The following image shows wizard to follow.
Figure 1: Package Designer’s Advance tabIn the “Add existing Assembly” window, add the following namespaces for Ajax Control Toolkit.
The following image shows the “Add Existing Assembly” window for AjaxControlToolkit dll.
Figure 2: Add/Edit Existing Assembly windowNow you can build and deploy the package and as a result of deployment, Ajax Control Toolkit namespaces will be registered as safe controls in web.config.