Visual Studio & Silverlight Development Tools

Re: Re: WCF Issues...

umarkashmiri — Fri, 24 Oct 2008 09:57:05 GMT

I think, you should use the WCF service instead of WCF-silverlight enable one.It is more easy to understand.Like RPC work in Java platform.
It will make one interface for function prototyping and one class for implementation of those functions.
Thanks

Re: Re: WCF Issues...

Psychlist1972 — Sun, 21 Sep 2008 17:17:52 GMT

Tom, can you provide a little more information about the problem you're encountering?

Pete

Re: Re: WCF Issues...

tom.winans — Fri, 19 Sep 2008 19:59:53 GMT

I see this on Win 2K8 ...

Re: Re: Re: WCF Issues...

german00 — Wed, 25 Jun 2008 15:13:55 GMT

Excelent Work

Excelente, Funciona !!!!!

Re: Re: Re: WCF Issues...

RodKestler — Fri, 20 Jun 2008 17:37:55 GMT

Also, to supplant sladapter's information, here are the size and version stamps for each version of Microsoft.VisualStudio.ServicesProxy.dll:

The incorrect version is:

Version: 9.0.21116.54

Size: 56.0 KB

The correct version (after removing and reinstalling Silverlight 2 Beta 2 Toolkit for Visual Studio 2008) is:

Version: 9.0.21022.108

Size: 36.0 KB

Re: Re: WCF Issues...

KevD — Fri, 13 Jun 2008 07:17:16 GMT

Just thought I'd give a quick update: my problem is solved!

I was using a (correct) crossdomain.xml-file. I changed this to clientaccesspolicy.xml and pasted the correct xml into it:

<?xml version="1.0" encoding="utf-8"?>
<access-policy>
<cross-domain-access>
    <policy>
      <allow-from http-request-headers="*">
        <domain uri="*"/>
      </allow-from>
      <grant-to>
        <resource path="/" include-subpaths="true"/>
      </grant-to>
    </policy>
</cross-domain-access>
</access-policy>

... and all of a sudden, my WCF-calls work again! Don't know why the crossdomain.xml-file isn't supported anymore, but: problem solved!

Tnx for the help guys!

Re: Re: WCF Issues...

sladapter — Thu, 12 Jun 2008 15:42:16 GMT

I don't know why VS added some invalid tag in the clientconfig. You might want to report that as a bug in bug forum and see if they have some explanation.

The work around would be not relying on the clientconfig file. Just set the address and binding in the code, just like we did in beta 1. Otherwise you have to keep modifying your clientconfig all the time until they fix that bug.

System.ServiceModel.BasicHttpBinding binding = new System.ServiceModel.BasicHttpBinding();
        //If you want to specify non default message size, you can do it
        binding.MaxReceivedMessageSize = 2147483647; // int's max size , (those two lines are optional, depending your need.)
        binding.MaxBufferSize = 2147483647; // int's max size

System.ServiceModel.EndpointAddress address = new System.ServiceModel.EndpointAddress(new Uri(Application.Current.Host.Source, "../YourService.svc"));

~~var webService = new YourService.YourSeviceClient();~~ // this is the default constructor, it will read binding and address from the config file, do not use this one

var webService = new YourService.YourSeviceClient(binding, address);

So it will bypass the clientconfig reading.

Re: Re: WCF Issues...

Rui-Marinho — Thu, 12 Jun 2008 15:24:56 GMT

its working, i deleted the custombinding and it works, but evry time i do update service the clientconfig adds that custombinding, so its from my webservice right? because it is asmx????

thanks once again slapadapter :)

Re: Re: WCF Issues...

sladapter — Thu, 12 Jun 2008 14:13:51 GMT

Rui-Marinho,

How did you create the customBinding ? I put that section in my .ClientConfig file I can see <customBinding> Tag is invalid. I think that is your problem. I did not even see where you use that binding. You are using DataServiceSoap which is the basicHttpBinding. I think current Silverlight still just support basicHttpBinding. Try to remove that customBinding and try it.

Re: Re: WCF Issues...

martintr — Thu, 12 Jun 2008 11:28:13 GMT

Re: Re: WCF Issues...

Rui-Marinho — Thu, 12 Jun 2008 10:52:59 GMT

slapadapter it works weel on silverlight 2 beta 1, but not in beta 2, could it be the instalation file?

i clear the config and re-add the service, but i still have the same error:

here goes my clientconfig

<system.serviceModel>

</binding>

</basicHttpBinding>

<textMessageEncoding maxReadPoolSize="64" maxWritePoolSize="16"

messageVersion="Soap12" writeEncoding="utf-8">

<readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"

maxBytesPerRead="4096" maxNameTableCharCount="16384" /> </textMessageEncoding>

<httpTransport manualAddressing="false" maxBufferPoolSize="524288"

maxReceivedMessageSize="65536" allowCookies="false" authenticationScheme="Anonymous"

bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"

keepAliveEnabled="true" maxBufferSize="65536" proxyAuthenticationScheme="Anonymous"

realm="" transferMode="Buffered" unsafeConnectionNtlmAuthentication="false"

useDefaultWebProxy="true" />

</binding>

</customBinding>

</bindings>

<endpoint address="http://iffiretv.ifthensoftware.com/DataService.asmx"

binding="basicHttpBinding" bindingConfiguration="DataServiceSoap"

contract="iffiretv_beta2.DataServiceProxy.DataServiceSoap"

name="DataServiceSoap" />

</client>

</system.serviceModel>

</configuration>

Re: Re: WCF Issues...

Rui-Marinho — Thu, 12 Jun 2008 10:52:56 GMT

i clear the config and re-add the service, but i still have the same error:

here goes my clientconfig

<system.serviceModel>

</binding>

</basicHttpBinding>

<textMessageEncoding maxReadPoolSize="64" maxWritePoolSize="16"

messageVersion="Soap12" writeEncoding="utf-8">

<readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"

maxBytesPerRead="4096" maxNameTableCharCount="16384" />

</textMessageEncoding>

<httpTransport manualAddressing="false" maxBufferPoolSize="524288"

maxReceivedMessageSize="65536" allowCookies="false" authenticationScheme="Anonymous"

bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"

keepAliveEnabled="true" maxBufferSize="65536" proxyAuthenticationScheme="Anonymous"

realm="" transferMode="Buffered" unsafeConnectionNtlmAuthentication="false"

useDefaultWebProxy="true" />

</binding>

</customBinding>

</bindings>

<endpoint address="http://iffiretv.ifthensoftware.com/DataService.asmx"

binding="basicHttpBinding" bindingConfiguration="DataServiceSoap"

contract="iffiretv_beta2.DataServiceProxy.DataServiceSoap"

name="DataServiceSoap" />

</client>

</system.serviceModel>

</configuration>

Re: Re: WCF Issues...

kobyb — Thu, 12 Jun 2008 07:37:00 GMT

Hi,

I get the same problem as @sunraybrett and @KevD - The remote server returned an unexpected response: (404) Not Found

Here is a print screen of the HTTP log:

Any ideas?

Thanks,
Koby

Re: Re: WCF Issues...

sladapter — Wed, 11 Jun 2008 18:59:15 GMT

Rui-Marinho,

I looked at your error message again. You might want to check your ServiceRefrence.ClientConfig file to see anything strange there, can you see any invalid Tag in that file? That file is used by ServiceClient in beta 2. In beta1, this file is not used.

You can try to delete your ServiceReference first, make sure the ClientConfig file is empty. Then re-add the ServiceReference back and try it.

Re: Re: WCF Issues...

sladapter — Wed, 11 Jun 2008 18:50:28 GMT

Take a look at this thread, you might find something. There are a lot of WCF related problems in beta 2. Not a single solution can fix them all. You have to find one for yourself. By the way, you said your service call had no problem in SL 1. Have you tried it in SL2 beta 1? Or you meant it worked fine in beta 1?

http://silverlight.net/forums/t/17733.aspx