I've made about two or three ASP.NET 1.1 projects, all using this brilliant Ajax.Net library, and they all worked perfectly. Then I've created one NET2.0 web application and used Ajax.Net Pro. Tested it, worked, published it, only to see that the client (the man ordering the project :)) doesn't see it work. The code, as simple as possible, was instantiating a Web UserControl with LoadControl(..) and then returned the html output. A javascript function was changing the innerHTML property of a panel to display it. It worked on Ie6.0, FireFox, Opera and Netscape. It also worked on some other people's computers. The client only saw a "null" appearing where the panel should have been. Now, my manager is against testing stuff on the machines of the client, so the only thing I know is this: 1. the application works on all browsers, it is not a matter of ActiveX disable or bad javascript 2. the javascript code does something like if (response.error!=null) alert(response.error); and it doesn't fire, so it is not a server error 3. the javascript code uses callback functions, so it's not a delay issue. 4. the only way to have the same result on my computer was to have response.error==null, response.value==null which I don't see how it could happen.
The only thing I could think of was that the client uses both a web proxy and a firewall. Could that be the problem? How do I fix it? Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
