I have a wildcard mapping in IIS for '.*' that maps to asp.net's dll to handle any mapping not specified in IIS with asp.net.
For some reason having this wildcard mapping in IIS breaks atlas. It appears that the javascript proxy no longer works. I.E.'http://localhost/MyService.asmx/js' returns a error 'The resource cannot be found'. If I remove the wildcard ('.*') mapping from IIS then the atlas code starts to work.
Has anyone else experienced this problem, or know a way that I can have a wildcard mapping in IIS and still use atlas in my application?
Hi Zerobit,
I also experienced the same when i added the wildcard as '.*' in configuration section of the project in INETMGR. can anyone help us why the wild card is creating the problem ??
Regards,
Kathir
Someone posted this in another thread where I asked the same question:
"I added a folder named "Webresource.axd" (without quotes) to the root of my application and ATLAS works now with a wildcard mapping in IIS. I hope this trick will solve the issues you are experiencing."
I havn't tested it as I have since switched to AjaxPro. But if it works let me know.
No comments:
Post a Comment