locked
clientaccesspolicy RRS feed

Answers

  •  

     

    The policy file should not be "inside the SilverlightApp.Web".

    IF you have a cross domain issue, Silverlight will look for the policy file at http://localhost:3927 - the root of the domain.


    As mentioned, if you're hosting on IIS (or any web server), you need to place the file in the physical folder that represents the virtual directory "http://localhost:3927".

    If you are self-hosting the web app (unlikely since I'm guessing your *.Web project is an ASP.NET app), you can provide the policy file via a web service.  For example:  Enabling cross-domain calls for Silverlight apps on self-hosted web services

     

     

     

    Friday, January 8, 2010 4:31 PM
  • Hi mothilal,

    Do you have a need for the clientaccesspolicy.xml file?  Are you planning to separate the service and the web page hosting your Silverlight app at some future deployment?

    Generally, the SilverlightApp is built and hosted on a web page in the SilverlightApp.Web site.  If you are hosting your service at SilverlightApp.Web, which I'm assuming since you're placing the clientaccesspolicy.xml file there, the Silverlight app will consider that to be a site of origin call and won't check for a clientaccesspolicy file.

     

    Friday, January 8, 2010 5:25 PM

All replies

  • Cross Domain error will not prompt on VS Developer Server

    If it is in case on IIS, you have to put the clientaccesspolicy on the root

    btw, remember to set the endpoint address of the service correctly

    Friday, January 8, 2010 4:19 AM
  •  

     

    The policy file should not be "inside the SilverlightApp.Web".

    IF you have a cross domain issue, Silverlight will look for the policy file at http://localhost:3927 - the root of the domain.


    As mentioned, if you're hosting on IIS (or any web server), you need to place the file in the physical folder that represents the virtual directory "http://localhost:3927".

    If you are self-hosting the web app (unlikely since I'm guessing your *.Web project is an ASP.NET app), you can provide the policy file via a web service.  For example:  Enabling cross-domain calls for Silverlight apps on self-hosted web services

     

     

     

    Friday, January 8, 2010 4:31 PM
  • Hi mothilal,

    Do you have a need for the clientaccesspolicy.xml file?  Are you planning to separate the service and the web page hosting your Silverlight app at some future deployment?

    Generally, the SilverlightApp is built and hosted on a web page in the SilverlightApp.Web site.  If you are hosting your service at SilverlightApp.Web, which I'm assuming since you're placing the clientaccesspolicy.xml file there, the Silverlight app will consider that to be a site of origin call and won't check for a clientaccesspolicy file.

     

    Friday, January 8, 2010 5:25 PM