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

More Search Options

RSS Available

• Re: Problem with ScriptManager.RegisterOnSubmitStatement and Partial Update

  I just ran into the exact same problem. They should definitely be cleared. I'll ping a dev on the team and ask him about it.

  Posted to ASP.NET AJAX UI (Forum) by JRumerman on 8/6/2008

• Re: Where is an ASP.NET Thread's Culture Initially Set?

  Hi Vivek (and everyone else), That is what I initially guessed, but that's not the case. Here's the reflected code from the InitializeCulture method on the Page object: protected virtual void InitializeCulture() { } It seems that the InitializeCulture method is where we can override the culture, but it's not where it's initially set. I'm looking for the location where the header value Accept-Language is read and processed automatically. I read through the post that you pointed

  Posted to Localization (Forum) by JRumerman on 1/8/2008

• Where is an ASP.NET Thread's Culture Initially Set?

  Hi Everyone, I was wondering if anybody knew where an ASP.NET thread's culture was initially set. Where is Accept-Language: en-US translated to the Culture Info assigned to the running thread? At first I thought it was going to be somewhere in the Page class, but that is obviously too limiting (what about web services?). I followed the little white rabbit into WebHeaderCollection and UnsafeNclNativeMethods, but I've lost sight of the rabbit. Anybody already figured this one out? Thx, Joel

  Posted to Localization (Forum) by JRumerman on 1/7/2008

• Re: Bug in parseLocale with French Numbers

  Well, I just wanted to add another example: < %@ Page Language= "C#" AutoEventWireup= "true" CodeFile= "FrenchTest.aspx.cs" Inherits= "FrenchTest" %> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> < html xmlns= "http://www.w3.org/1999/xhtml" > < head runat= "server" > < title >Untitled Page</ title > </ head

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by JRumerman on 1/4/2008

• Bug in parseLocale with French Numbers

  Hi Everyone, I think I've come across a problem with the Number.parseLocale method when working with French formatted numbers when the value is greater than 999. Number.parseLocale( "1 234,88" ); In the French culture, a string displayed like the following: 1 234,88 means 1,234.88 in the English (en) culture. However, when the string is passed into the Number.parseLocale method, it fails because it isn't recognized as a valid float. From looking at the code, I figured out that the

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by JRumerman on 1/2/2008

• Re: AJAX compression and caching not working on ScriptResource.axd files.

  Not that you care anymore since that message was from March, but yea, you're right. Here's the code from reflector that determines if compression is enabled. private static bool IsCompressionEnabled(HttpContext context) { if (!ScriptingScriptResourceHandlerSection.ApplicationSettings.EnableCompression) { return false ; } if ((context != null ) && context.Request.Browser.IsBrowser( "IE" )) { return (context.Request.Browser.MajorVersion > 6); } return true ; } My guess

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

• Re: Calling Asynchronous Web Services

  [quote user="korggy"] ... asynchronous web methods are basically a server-side construct that provides a framework within which you can return a thread to the pool until some long-running process completes. [/quote] That's absolutely correct. Only MethodName is in the WSDL, and the handling of the Begin<MethodName> and End<MethodName> requests is done by an implementation of the IHttpAsyncHandler. When AJAX interrogates the web methods (using reflection, you are correct

  Posted to ASP.NET AJAX Networking and Web Services (Forum) by JRumerman on 8/1/2007

• Re: Calling Asynchronous Web Services

  I got ya... but there's no way to do it The RESTHandler that handles our request when we execute a client call to a web service method we've tagged as a ScriptMethod is synchronous. It implements IHttpHandler, not IHttpAsyncHandler. I've gotten different responses from MSFT regarding why this is the case, but it seems that the consensus was that since the next version of ASP.NET AJAX supports calling WCF methods and those don't have to use ASP.NET threads anyways (they can live at

  Posted to ASP.NET AJAX Networking and Web Services (Forum) by JRumerman on 8/1/2007

• Re: Calling Asynchronous Web Services

  When using asynchronous web services does the "work" move to a new background thread or does it still remain on an ASP.NET thread? (A similar pattern to using an IHttpAsyncHandler.) If it does move to a non-ASP.NET thread then that would be a good reason to use the asynchronous web service pattern, even though AJAX is an asynchronous pattern as it provides scalability for the website because ASP.NET has a limited number of threads available. But, again, I'm not sure if the work moves

  Posted to ASP.NET AJAX Networking and Web Services (Forum) by JRumerman on 7/31/2007

• Re: RegisterServices in AsyncPostBack

  It's unfortunate that I can't use ServiceReferences directly. I like Kazi's suggestion the most of what I've heard so far so I'll work with that.

  Posted to ASP.NET AJAX Networking and Web Services (Forum) by JRumerman on 7/31/2007