![](\"http:\/\/www.itwriting.com\/images\/vbsilverlighterror.gif\")
<\/p>\nAnother in my recent series on getting Silverlight 2.0 beta 2 working.<\/p>\n
If you create a WCF web service for Silverlight, it\u2019s well known that on the server side you have to change the binding to basicHttpBinding (or use the new Silverlight-enabled WCF service). Then you can use the Add Reference wizard in your Silverlight application and code against the generated ServiceClient. <\/p>\n
This works in C#, but in VB you may hit this error at runtime:<\/p>\n
<\/p>\n
The error is \u201cCould not find endpoint element\u201d etc, and it refers to your \u201cclient configuration section\u201d.<\/p>\n
I fixed this by comparing the ServiceReferences.ClientConfig file generated in a VB project with that for a C# project. Check the Contract attribute of the endpoint element. It should be qualified with the full namespace, by default the name of your app. In this example, it would be:<\/p>\n
\ncontract="RegSilverlightDemoApp.RegService.IRegService"<\/p>\n<\/blockquote>\n
However, the VB wizard omits the first part of the namespace; then at runtime, it can\u2019t find the service.<\/p>\n
Evidence, perhaps, that C# is the language of choice in Microsoft\u2019s developer division.<\/p>\n
Technorati tags: silverlight<\/a>, vb<\/a>, wcf<\/a>, visual studio<\/a>, visual basic<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"Another in my recent series on getting Silverlight 2.0 beta 2 working. If you create a WCF web service for Silverlight, it\u2019s well known that on the server side you have to change the binding to basicHttpBinding (or use the new Silverlight-enabled WCF service). Then you can use the Add Reference wizard in your Silverlight … Continue reading Fixing a Silverlight 2.0 WCF reference in a VB application<\/span>