hello guys.

can anyone tell me why the behavior of the traditional proxy generation has changed in this last ctp? till now, we could get the proxy by doing something like this:

<script type="text/javascript" src="path/js"></script>

currently, this returns the proxy but doesn't set the path property of the proxy...

yes, i can see that you guys changed the generatefields method of the webserivceclientproxygenerator class...what i'd like to know is:

1.) why isn't this documented?

2.) why is this changed necessary?

btw, this change breaks all your online demos (including videos, quickstarts, etc)....

btw, what's the purpose of theonscriptload attribute that has been added to the servicereference class?

The change was made to fix the issue where the path was incorrect due to the fact that we were computing the path with respect to the server as opposed to the client, i.e. webfarm scenarios, port forwarding.  So now the client sets the path to the url it uses to access the site via the OnScriptLoad method which you see.  Perhaps we should add the old behavior back as a default for the direct /js include scenario.

Thanks for reporting this,
-Hao

I should also mention that we did add a new query string parameter for the /js requests which supports generating a path in the proxy, but its explicit, i.e. you pass in the path:

<script src=testSoap.asbx/js?__svcPath=http://localhost/atlas/BCL/testSoap.asbx" type="text/javascript"></script>

Hope that helps,
-Hao

hello.

thanks for the reply.

can you give me an example of how to use that new property?

Its basically whatever script you want to be evaluated, so scriptLoad="alert('hi')" or something like what we do scriptLoad="Sample.ProxyClass.path = 'http://url/app/fooservice.asmx'".

Hope that helps,
-Hao

hello again.

hum,...i must have done something wrong because i tried something like that and it did not work...i'll give it a go again. thanks.

I ran into the same problem today. I used to include a script reference to a webservice dynamically (webpart code) using

ScriptManager.GetCurrent(Page).RegisterScriptReference(Page.ResolveUrl("~/Service.asmx/js"));

After I found out that calls were made to "undefined?mn=xxx", I changed it to

ScriptManager.GetCurrent(Page).RegisterScriptReference(Page.ResolveUrl("~/Service.asmx/js?__svcPath=Service.asmx"));

This works, but it does looks a bit redundant to me :(