Wednesday, July 16, 2008 10:53 PM marcochila

ClientCallback... very poor...

I'm not an expert but I got some experience around web development and I can say that ClientCallback calls seem to be very poor to me... I'm working around a real world example on my job, we are moving from VS2003 to VS2008, and I'm writing more code on VS2008 than with VS2003 and AjaxPro.

I guess the model that AjaxPro works on is more produtive and intuitive than the GetCallbackEventReference model used by ClientCallback.

Using AjaxPro we just add the attribute that a method is a webmethod and you could call it from your client code but in VS2008 things are worst. On my applications I need to look up on a database when a text if filled and the javascript onBlur method is fired. Then, an XML will retunr with or not some data and everything is right.

Well, that's for now... I'll keep working, maybe I can discover something that make me change my first opinion...

See you!@!

Chilá!@!

Filed under: , ,

Comments

# re: ClientCallback... very poor...

Wednesday, July 16, 2008 11:23 PM by Joe Chung

You may want to check out ASP.NET Ajax, PageMethods in particular.

# re: ClientCallback... very poor...

Thursday, July 17, 2008 12:05 AM by marcochila

Joe Chung, thank you for your advice... I'll check it out...

See you..

# re: ClientCallback... very poor...

Thursday, July 17, 2008 3:23 AM by Ian Blackburn

Have you looked at the Ajax Extensions for asp.net that replaced the clientcallback framework?

http://ajax.asp.net

# re: ClientCallback... very poor...

Thursday, July 17, 2008 11:02 AM by marcochila

Ian, I'm testing right now the pagemethods... It's great for me because as I told before I'm moving from AjaxPro to ASP.NET AJAX and from VS2003 to VS2008.

The following post from Michael Scharwz explain how to move from one to another...

weblogs.asp.net/.../how-to-move-from-ajaxpro-to-asp-net-ajax-pagemethods.aspx

thank you for your comment...

Leave a Comment

(required) 
(required) 
(optional)
(required)