Sunday, March 11, 2012

Problem when interacting with Webservice

I can think of two possible problems off the top of my head. Not positive, as I didn't test what you did, but I know what I'm going to tell you works, so I'm comparing the differences.

first, I think it's a good idea to put the Scriptmanager in the <head> and I'd put it before your other javascript functions. I realize that that might not matter, but I just like (for my own sanity) to keep that scriptmanager in the <head>.

Further, I've not seen before the technique of calling the service's script proxy directly in the scriptmanager. what I've seen instead is calling the service itself as part of teh <services> collection like so:

<atlas:ScriptManager id="scm" runat="server">
<Services>
<atlas:ServiceReference Path="atlasWebService1.asmx" />
</Services>
</atlas:ScriptManager>

No comments:

Post a Comment