Silverlight cross-origin access WebService Solution

This may be because there is no correct cross-origin policy when attempting to access the service in the Cross-origin mode, or the policy is not applicable to the SOAP service. You may need to contact the service owner to publish a cross-domain policy file and ensure that the file allows sending HTTP headers related to SOAP. This error may also occur because the internal type in the Web Service proxy is used, but the InternalsVisibleToAttribute attribute is not used.

When using Silverlight to call WebService, the following error occurs:

This may be because there is no correct cross-origin policy when attempting to access the service in the Cross-origin mode, or the policy is not applicable to the SOAP service. You may need to contact the service owner to publish a cross-domain policy file and ensure that the file allows sending HTTP headers related to SOAP. This error may also occur because the internal type in the Web Service proxy is used, but the InternalsVisibleToAttribute attribute is not used.

Cause:

Silverlight accesses other server data through WebService. S

Solution: create a cross-origin policy file:

Create two XML files in the root directory of the Silverlight Website:

ClientAccessPolicy. xml

<? 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>

Crossdomain. xml

<? Xml version = "1.0"?>

<! DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">

<Cross-domain-policy>

<Allow-access-from domain = "*"/>

<Allow-http-request-headers-from domain = "*" headers = "*"/>

</Cross-domain-policy>