Skip to main content

Silverlight cross-domain trouble

The last days I’m spending some time learning Silverlight. And as a newbie, I’m making all the beginner mistakes (and learning a lot from it).

One of the obvious things you need to do if your Silverlight application is calling out to external webservices is to enable cross-domain calls.

Most of the time you get an error message like this:

“An error occurred while trying to make a request to URI ‘http://localhost:1378/MyFirstSilverlightService.svc’. This could be due to attempting to access a service in a cross-domain way without a proper cross-domain policy in place, or a policy that is unsuitable for SOAP services. You may need to contact the owner of the service to publish a ……...”

To solve this you have to add a clientaccesspolicy.xml file in the root folder where your services are hosted. Insert the following lines:

   1:  <?xml version="1.0" encoding="utf-8"?>
   2:  <access-policy>
   3:    <cross-domain-access>
   4:  <policy>
   5:        <allow-from http-request-headers="*">
   6:          <domain uri="*"/>
   7:        </allow-from>
   8:        <grant-to>
   9:          <resource path="/" include-subpaths="true"/>
  10:        </grant-to>
  11:      </policy>
  12:    </cross-domain-access>
  13:  </access-policy>

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...