You searched for the word(s): userid:666923

More Search Options

RSS Available

• Re: Another ScriptManager RegisterScriptDescriptors problem

  The order in which the script descriptors set the client-side object properties is totally arbitrary. It is in fact sloppy coding to rely on the order of assignment. A possible solution when properties depend on each other is to detect when the control has not yet been initialized (the initialize method has not run) during execution of the setter methods. When the setter runs before initialization you can create a pending property assignment that is executed inside the initialize method. You can

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by dotnetsamurai on 10/11/2007

• Re: Webmethod doesn't get called.

  Off course the debugger won't step into a method that doesn't execute. You should check out these tutorials about exposing a web service to the client and consuming a web service in the client ( http://www.asp.net/AJAX/Documentation/Live/tutorials/ExposingWebServicesToAJAXTutorial.aspx , http://www.asp.net/AJAX/Documentation/Live/tutorials/ConsumingWebServicesWithAJAXTutorial.aspx ) You need to register the web service with the script manager. Also, it is easier and more efficient to use

  Posted to ASP.NET AJAX Networking and Web Services (Forum) by dotnetsamurai on 10/11/2007

• How to set the MaxJsonLength for ScriptManager.RegisterScriptDescriptors?

  I am creating a ScriptControl with a ScriptControlDescriptor property larger than the default maximum allowed by the JavaScriptSerializer. I need to set the MaxJsonLength property of the JavaScriptSerializer that is used by RegisterScriptDescriptors. I tried setting the MaxJsonLength of the ScriptingJsonSerializationSection (see http://forums.asp.net/p/1067690/1548990.aspx#1548990 ), but that had no effect because it only applies to the JavaScriptSerializer used by the asynchronous communication

  Posted to ASP.NET AJAX Networking and Web Services (Forum) by dotnetsamurai on 10/11/2007

• Re: JavaScriptSerializer.Deserialize<DateTime>(string) has undocumented UTC conversion

  Unfortunately I never did find the answer to this problem. I hope somebody provides an answer here.

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by dotnetsamurai on 10/11/2007

• Re: IIS Javascript Issues

  As this post says http://forums.asp.net/p/1054927/1745730.aspx#1745730 it is a good idea to cleanly uninstall remove the CTP before installing the RTM

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by dotnetsamurai on 6/8/2007

• Re: IIS Javascript Issues

  Hi dashnash I encountered exactly the same error with a deployment. My web app worked on all deployments except one that had this error. I discovered that server with the bad deployment had an older version of Ajax Extensions (I think it was the release candidate). This version has the exact same version number and public key token as the RTM version of Ajax Extensions, so when the dlls were copied into the windows GAC, nothing actually happened. Even though my web app was compiled with and required

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by dotnetsamurai on 6/8/2007

• Re: Update progress does not appear if control which triggers update is outside UpdatePanel

  Your absolutely right sudeepghatak It seems that AJAX Extensions is completely unaware of which update panel(s) is/are updating until the updates come back from the server. The only exception to this is when a child of an update panel postbacks and it is a trigger of the update panel. Then Ajax Extensions merely follows the parent references of the postback control to find which update panel it is inside. This creates an unfortunate limitation that an UpdateProgress control either updates for every

  Posted to ASP.NET AJAX UI (Forum) by dotnetsamurai on 6/1/2007

• Re: Problem with custom Profile Property datatype

  I got the same error recently. In my case the problem was that the type was nested in a class. I moved it from a nested class to its own class in the namespace and the error went away.

  Posted to Web Parts and Personalization (Forum) by dotnetsamurai on 5/15/2007

• JavaScriptSerializer.Deserialize<DateTime>(string) has undocumented UTC conversion

  Consider this code: 1 JavaScriptSerializer jss = new JavaScriptSerializer(); 2 string jsonTime = jss.Serialize(DateTime.Now); 3 DateTime restoredTime = jss.Deserialize(jsonTime); 4 DateTime toLoc = restoredTime.ToLocalTime(); One would expect restoredTime to be the same as the DateTime created by DateTime.Now. All I do here is serialize to JSON then serialize back to DateTime. To my surprise, this is not the case. JavaScriptSerializer.Deserialize<DateTime> assumes that the JSON time representation

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by dotnetsamurai on 5/4/2007

• Re: JSON Date Serialization fails

  Here is a good explanation that comes from ( http://msdn2.microsoft.com/en-us/library/bb299886.aspx ) ASP.NET AJAX: Inside JSON date and time string The AJAX JSON serializer in ASP.NEXT encodes a DateTime instance as a JSON string. During its pre-release cycles, ASP.NET AJAX used the format " @ticks@ ", where ticks represents the number of milliseconds since January 1, 1970 in Universal Coordinated Time (UTC). A date and time in UTC like November 29, 1989, 4:55:30 AM would be written out as " @62831853071

  Posted to ASP.NET AJAX Networking and Web Services (Forum) by dotnetsamurai on 5/4/2007