title: Silverlight clientaccesspolicy.xml bug? or design?
body: <p>In the domain node of a clientaccesspolicy file you can specify a wildcard for a sub domain or protocol, but it would appear not for a port.</p>
  
  <p>Specifically when developing, if the service consumed is hosted on a third party, then access from a local debug version of a silverlight app running on the localhost asp.net development server works fine with the nodes:</p>
  
  <pre><code>&lt;domain uri="*"/&gt;
  &lt;domain uri="http://*"/&gt;
  &lt;domain uri="http://localhost:1234"/&gt; 
  </code></pre>
  
  <p>(where 1234 is the specific determined port number)</p>
  
  <p>but it would appear not to work if specified in the form</p>
  
  <pre><code>&lt;domain uri="http://localhost:*"/&gt;
  </code></pre>
  
  <p>which is extremely annoying if there are multiple developers/projects using the service or you do not specify a port for the asp.net development server</p>
  
  <p>Does annyone know if I am simply getting the format incorrect or is this either a bug or an oversight in the handling of the clientaccesspolicy by silverlight?</p>