New class ClientScript

Wednesday, November 19, 2003

.NET

Thanks Roy for the link to Brad Adams about 'Dirty unofficial list of classes to be removed in Whidbey'.

The one which get my attention is about the new ClientScript. So does it means we are going to have more control on client side scripting. Cool.

System.Web.UI.Page.IsClientScriptBlockRegistered	Use ClientScript.IsClientScriptBlockRegistered(string key) instead.
System.Web.UI.Page.IsStartupScriptRegistered	Use ClientScript.IsStartupScriptRegistered(string key) instead.
System.Web.UI.Page.RegisterArrayDeclaration	Use ClientScript.RegisterArrayDeclaration(string arrayName, string arrayValue) instead.
System.Web.UI.Page.RegisterClientScriptBlock	Use ClientScript.RegisterClientScriptBlock(string key, string script) instead.
System.Web.UI.Page.RegisterHiddenField	Use ClientScript.RegisterHiddenField(string hiddenFieldName, string hiddenFieldInitialValue) instead.
System.Web.UI.Page.RegisterOnSubmitStatement	Use ClientScript.RegisterOnSubmitStatement(string key, string script) instead.
System.Web.UI.Page.RegisterStartupScript	Use ClientScript.RegisterStartupScript(string key, string script) instead.

Do you know if there will be any backwards compatability for controls/sites currently using System.Web.UI.Page.~ instead of ClientScript.~ ? If they depreciate this, its going to be a pain in the neck for all server control developers.

Matt Hawley - Wednesday, November 19, 2003 1:14:00 PM

Well Matt this is just a first draft, but I believe that we will have to rewrite some parts. Good question anyway

Paschal - Wednesday, November 19, 2003 1:27:00 PM

2 Comments