Problem using SIlverLight to connect to WSA

Posted by simonhodgson on 27-Jun-2010 04:09

Hi

As result of Face2Face meeting of 2 weeks ago am exploring use of SilverLight however when I try to make connection through a new service am getting an error back.

I think this may be due to Soap 1.1 and Soap 1.2 or Silverlight defaulting to binary messages.

Does anyone have any ideas?

Message back is

"The HTML document does not contain Web service discovery information.

Metadata contains a reference that cannot be resolved: 'http://localhost:8080/wsa/PharmInfo'.


Content Type application/soap+xml; charset=utf-8 was not supported by service

http://localhost:8080/wsa/PharmInfo.  The client and service bindings may be mismatched.

The remote server returned an error: (415) Unsupported Media Type.


If the service is defined in the current solution, try building the solution and adding the service reference again."

Regards

SImon Hodgson

All Replies

Posted by Shelley Chase on 29-Jun-2010 16:47

Hi Simon,

I did this a few months back with Silverlight 2. I have upgraded my system to Silverlight 3 and I am getting errors running my old Silverlight projects after converting. I will take a look and let you know what I find out in the next couple of days. What version of Visual Studio and Silverlight are you using?

Posted by simonhodgson on 30-Jun-2010 16:27

Hi Shelley

Thanks for getting back to me.

Am using the latest version of SilverLight and Visual Studio 2010 downloaded test.

Also have a copy of Visual Studio 2008.

I have a suspicion it is something to do with ASP.NET because I did get a connection to TomCat once and the normal test screen came up as per making a connection

through internet explorer http://localhost:8080/wsa etc after I unistalled ASP.NET and re-installed.

It then did not work again

I am wnodering though if I need to do it this way.  Am not that familiar with Visual Studio but want to develop a web connection to my application for "light weight" users.

Regards

Simon Hodgson

Posted by simonhodgson on 01-Jul-2010 06:28

Hi Shelley

Have also now tried with Visual Studio and Visual Basic and getting the same error.

Regards

Simon.

This thread is closed