Advanced Forum Search Results
-
I would have to try it to be sure, but I believe that blocking the UI thread waiting for network call completion will deadlock in at least some of the supported browsers. The reason for this is that under the covers the browser raises the network completion callback on the UI thread; if that thread is blocked waiting for completion, ...
-
No the callback will be executed on a background (non-UI) thread. if you need to do UI updates in your callback method, the best way to handle this is as follows:
use DependencyObject.Dispatcher.BeginInvoke() which takes an Action delegate (void method). all your UI elements are DependencyObject so they all have a .Dispatcher ...
-
Hi, thanks for the feedback. I wonder if either of these possibility would work for you:
a) you can pass an instance of any type to the Async() method and then use this in the event handler to distinguish which call is completing
b) you can cast the proxy to the [ServiceContract] interface type, eg IHelloWorld, and use the Begin method ...
-
I replied off thread as well. Just removing use="encoded" attribute from the WSDL won't do it; if the service describes itself as use="encoded" it won't be supported in Silverlight (except of course you can always handcraft the SOAP messages). Often internet web service will provide more than one version of ...
-
Hey there, sorry for the late reply but I just now saw this. This
is a bug in Beta 1, thanks for reporting it as we weren't otherwise aware of it. you can work around the bug using the
InnerChannel property which will return the correct type:
client.InnerChannel.Abort(); hope it helps
-
Our goal with Beta 2 is to support all WS-I Basic Profile compliant services out there. note one potentially significant "gotcha": the BP prohibits use="encoded" services and Silverlight 2 will not support them.
If you could send me a pointer to the service you're using I could try it out with the latest Beta 2 bits ...
-
You can ignore those warnings, they shouldn't be getting generated at all. I am working on getting rid of them right now, actually...
Yes, there are some known issues in Beta 1 consuming amazon and other internet web services, and sharepoint web services for that matter. Believe me, we are well aware of the issue. ...
-
The error will be delivered to you in your Completed event handler. here's an example:
ServiceReference1.HelloWorldClient client;
public Page()
...
-
There were a few known issues with interop with asmx-based web services, including sharepoint, in Beta 1. This will be fixed for Silverlight 2. The fix will be available with the next preview release of the VS tools for Silverlight. No need to switch to AJAX or what-not.
-
Access to the .ctor overloads that take the bool skipVisibility option are restricted (because turning off member visibility checks would be a security risk). If you're passing 'false' for this bool, use one of the overloads that don't take the parameter instead.