Thanks very much for your reply... But is there any work around for this problem, because if I go ahead as per your suggestion then it would not comply with the standards we are following. Please let me know if there is any alternate solution.
Regards Mani INeedADip wrote: > These AJAX calls do not trigger the ASP.NET page lifecycle. Your > InitializeComponent method does not get executed. > > The page (object) gets instantiated, so you do have access to private > variables, but again....all the other methods do NOT execute. Not the > OnLoad, PreLoad, Render, etc... > > You should instantiate your object within the method where the > AjaxMethod attribute is applied. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info/ Don't forget to read my blog at http://weblogs.asp.net/mschwarz/ The open source project is now located at http://www.codeplex.com/Wiki/View.aspx?ProjectName=AjaxPro -~----------~----~----~----~------~----~------~--~---
