> Hello,
>
[quoted text clipped - 63 lines]
> Thanks in advance,
> Cesar
First thing I notice is the webservice call. It is the same as what I was
using until I found the following link:
http://dotnetslackers.com/columns/ajax/ASPNETAjaxWebService.aspx
You will notice the call is different than the call which I found in a video
a while back. There is some other info in the article which might help you.
Hope this helps (it did me)
Lloyd Sheen
Cesar - 03 Dec 2007 19:04 GMT
Hello Lloyd,
Thanks a lot for your help. However as far as I can understand, my problem
had nothing to do with the call signature; althought I had not included the
"userContext" it worked by having both the web service app and the calling
aspx page on normal (live) virtual directories:
1) http://localhost/ajaxwebservice/WebService.asmx
2) http://localhost/ajaxcall/default.aspx
And of course having the ServiceReference path set to
"http://localhost/ajaxwebservice/WebService.asmx"
I just started checking on ajax by myselft and so far, all the documentation
(videos included as well) only use the webservice within the same web
application as to the calling aspx page. I have no problems at with adding
"normal" web references to vs2005 "virtual web sites" (e.g.
http://localhost:4983/myWebService/myWebService.aspx) from another "virtual
web site" as they certainly work ...
But this time it didn't work for me calling ajax enabled web services
(running on a vs2005 virtual web site) from another aspx page running on
another virtual web site.
I'm not sure if I'm doing wrong but I guess I'll only use now "live" virtual
directories when testing ajax stuff.
Not sure though if anyone else has experienced this situation ?
Thanks a lot.
Best regards,
Cesar
> > Hello,
> >
[quoted text clipped - 74 lines]
> Hope this helps (it did me)
> Lloyd Sheen