WebPartManager.EnableClientScript WebPartManager.EnableClientScript WebPartManager.EnableClientScript WebPartManager.EnableClientScript Property


Gets or sets a value that determines whether client-side scripting is enabled on the Web page that contains a WebPartManager control.

 virtual property bool EnableClientScript { bool get(); void set(bool value); };
public virtual bool EnableClientScript { get; set; }
member this.EnableClientScript : bool with get, set
Public Overridable Property EnableClientScript As Boolean

Property Value

A Boolean value that indicates whether client script can run on the page. The default value is true.


The EnableClientScript property provides a way for developers to disable client scripts. You might want to disable client scripting for security purposes, or to ensure that all users of a page will have a similar user experience, even if they use different browsers.

You can disable client scripting by adding an EnableClientScript attribute to the WebPartManager element on a Web page, as in the following line of declarative code:

<asp:webpartmanager id="manager" runat="server"

EnableClientScript="false" />

Also, developers could eliminate this property by inheriting from the WebPartManager class and setting the default value to false.

The Web Parts control set uses client scripting to provide some of the client user interface (UI) and personalization features. If you disable client scripting, Web Parts controls still work, but some features are disabled. The ability to drag controls into different zones is disabled, along with the ability to render verbs in a drop-down verbs menu in a control's title bar (the verbs are instead displayed as links in the control's title bar).

Applies to

See also