本文中的資訊都是收集來的,來源很多,無法一一列出,望見諒。內容僅作為個人的知識管理。
Windows SharePoint Services v3 是基於ASP.NET 2.0建置。 Microsoft ASP.NET AJAX 1.0在MOSS之後推出,因此在某些情況下,ASP.NET AJAX 和SharePoint之間存在一些相容性問題,這些問題將會在Windows SharePoint Services SP1中解決。在此之前要在SharePoint中使用ASP.NET AJAX技術,需要進行一些特殊的部署步驟。
注意:
UpdatePanel在webpart中使用會有所限制。詳細情況請查考ASP.NET AJAX的文檔。並不是所有的控制項都可以在UpdatePanel中使用。
如果啟用了輸出緩存,就無法使用ASP.NET AJAX,否則會發生錯誤。經典的性能與時效的矛盾。
在SharePoint中使用Microsoft ASP.NET AJAX 1.0技術帶來的好處:
可以形成一套完整的客戶端腳本資源庫,並累積一些可重複使用的部件。
可以使用JSON展示我們的Web服務資料, 結果可以很容易的在JavaScript/Ajax應用程式中使用。
利用擴充中的技術建構WebPart可以提供高互動性的樣式,例如一個具備自動完成功能的textbox.
在WebPart中利用UpdatePanel,實現無回呼的交互,減少刷新頁面的次數。
以下是部署使用了Microsoft ASP.NET AJAX 1.0技術的元件前的環境準備步驟。 (只需在新安裝的環境中部署一次,以後添加Webpart就不用了)
下載並在Web伺服器場上安裝ASP.NET AJAX
首先,必須安裝"ASP.NET 2.0 AJAX Extensions 1.0" ,可以從ajax.asp .net下載。
為Microsoft ASP.NET AJAX 1.0擴充SharePoint web.config
我們需要為Ajax註冊一些特定的條目。 編輯SharePoint的web.config文件,該文件通常位於如下目錄:
c:inetpubwwwrootwssvirtualdirectories80
新增
在
在
在HttpModules 節中加入下面的註冊內容,放在所有現有的註冊內容下面
在
最後,加入下面的configuration標記到web.config檔末尾, 在結束標記
利用AjaxBaseWebPart進行開發
編寫使用該擴充功能的WebPart最簡單的方法就是直接繼承別人寫好的AjaxBaseWebPart。下面是我用的一個。您也可以用其他的,或自己寫一個。
下面是命名空間引用部分:
using System;
using System.Collections.Generic;
using System.Text;
using System.Web;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
using System.Web.UI;
using Microsoft.SharePoint.WebPartPages;
using Microsoft.SharePoint.Utilities;
using System.Web.UI.WebControls;
using System.Drawing;
以下是AjaxBaseWebPart類別的實作部分:
///
/// A base class that implements all the functionality required to use ASP.net Ajax extensions inside WSS
///
[XmlRoot(Namespace = "Deps.AjaxBaseWebpart")]
public abstract class AjaxBaseWebpart : Microsoft.SharePoint.WebPartPages.WebPart
{
/*
* The idea and the code behind this base web part was taken from Erics blog post at:
* http://www.capdes.com/2007/02/ajaxbasepart_easy_aspnet_20_aj.html
* This basically manages the presence and configuration of the ScriptManager
* which is required by ASP.net ajax extensions to handle postbacks, ect. This web part also includes
* a common method for handling errors.
*/
#region Declarations
private string _ValidationGroupId;
private ValidationSummary _ErrorContainer;
private ScriptManager _AjaxManager;
#endregion
#region Constructor
public AjaxBaseWebpart()
{
}
#endregion
#region Methods
///
/// Used to provide a common way to display errors to the user of the current web part.
///
/// Description of the error that occured.
public void RegisterError(string message)
{
if (this.Controls.Contains(_ErrorContainer))
{
//this way of generating a unique control id is used in some of the OOB web parts
int uniqueCounter;
if (HttpContext.Current.Items["GetUniqueControlId"] != null)
{
uniqueCounter = (int)HttpContext.Current.Items["GetUniqueControlId"];
}
else
{
uniqueCounter = 0;
}
uniqueCounter++;
HttpContext.Current.Items["GetUniqueControlId"] = uniqueCounter;
//create a custom validator to register the current error message with the ValidationSummary control
CustomValidator cv = new CustomValidator();
cv.ID = string.Concat("_Error_", uniqueCounter);
cv.ValidationGroup = _ValidationGroupId;
cv.Display = ValidatorDisplay.None;
cv.IsValid = false;
cv.ErrorMessage = message;
this.Controls.Add(cv);
}
else
{
//if RegisterError is called before the CreateChildControls override in AjaxBasePart then transfer the user to an error page using the SPUtility
SPUtility.TransferToErrorPage("The CreateChildControls function of the AjaxBasePart has not been called. You probably need to add "base.CreateChildControls()" to the top of your CreateChildControls override.");
}
}
///
/// Needs to be called to ensure that the ValidationSummary control is registered on the page. Any child web parts will need to have base.CreateChildControls() at the top of their own CreateChildControls base.CreateChildControls() at the top of their own CreateChildControls override.
///
protected override void CreateChildControls()
{
base.CreateChildControls();
if (!this.Controls.Contains(_ErrorContainer))
{
_ValidationGroupId = Guid.NewGuid().ToString();
_ErrorContainer = new ValidationSummary();
_ErrorContainer.ID = "_ErrorContainer";
_ErrorContainer.ValidationGroup = _ValidationGroupId;
_ErrorContainer.BorderStyle = BorderStyle.Solid;
_ErrorContainer.BorderWidth = Unit.Pixel(3);
_ErrorContainer.BorderColor = Color.Red;
this.Controls.Add(_ErrorContainer);
}
}
#endregion
#region Events
///
/// Oninit fires before page load. Modifications to the page that are necessary to support Ajax are done here.
///
protected override void OnInit(EventArgs e)
{
base.OnInit(e);
//get the existing ScriptManager if it exists on the page
_AjaxManager = ScriptManager.GetCurrent(this.Page);
if (_AjaxManager == null)
{
//create new ScriptManager and EnablePartialRendering
_AjaxManager = new ScriptManager();
_AjaxManager.EnablePartialRendering = true;
// Fix problem with postbacks and form actions (DevDiv 55525)
Page.ClientScript.RegisterStartupScript(typeof(AjaxBaseWebpart), this.ID, "_spOriginalFormAction = document.forms[0].action;", true);
//tag:"form" att:"onsubmit" val:"return _spFormOnSubmitWrapperOnSubmitWrapperOnSubmitWrapperOnSubmitWrapperOnSubmitWrapperOnSubmitWrapperOnSubmitWrapperOnSubmitWrapperOnSubmitWrapper )" blocks async postbacks after the first one
//not calling "_spFormOnSubmitWrapper()" breaks all postbacks
//returning true all the time, somewhat defeats the purpose of the _spFormOnSubmitWrapper() which is to block repetitive postbacks, but it allows MS AJAX Extensions to work properly
//its a hack that hopefully has minimal effect
if (this.Page.Form != null)
{
string formOnSubmitAtt = this.Page.Form.Attributes["onsubmit"];
if (!string.IsNullOrEmpty(formOnSubmitAtt) && formOnSubmitAtt == "return _spFormOnSubmitWrapper();")
{
this.Page.Form.Attributes["onsubmit"] = "_spFormOnSubmitWrapper();";
}
//add the ScriptManager as the first control in the Page.Form
//I don't think this actually matters, but I did it to be consistent with how you are supposed to place the ScriptManager when used declaritevly
this.Page.Form.Controls.AddAt(0, _AjaxManager);
}
}
}
#endregion
#region Properties
///
/// Exposes the Page's script manager. The value is not set until after OnInit
///
[WebPartStorage(Storage.None)]
public ScriptManager AjaxManager
{
get { return _AjaxManager; }
設定 { _AjaxManager = value; }
}
#endregion
}
開發時只要繼承這個WebPart就可以加入UpdatePanel,並且在裡面加入其他控制項了。