Thanks, Shandy. It seems fairly obvious to me that one of two things are happening:
1) The <httpHandlers> specification in Web.config is being ignored for some reason. 2) Something in the system is blocking ASP.NET from routing the GET for the "JavaScript" .ashx files to the appropriate method in the AjaxPro .dll Either way the end result is that the server thinks the client is requesting files that aren't there. Knowing my luck, the problem is probably due to some obscure IIS, Security, ASP, or VS setting that everyone in the world has set differently than me, so no-one's ever going to be able to replicate it. ;o) Do you think there might be some server logs that would have some helpful information on tracking down what exactly is going wrong? Cheers, Joe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
