Issues related to using Silverlight in SharePoint

Silverlight is more and more applied to the Web development environment, and is no exception in SharePoint, and here are some notes about using Silverlight in SharePoint 2010:

1, IE version problem: Silverlight of the XAP file in the 64bit IE can not be loaded, so, please use the 32bit of IE to load.

2. Safari browser support problem: Silverlight WebPart does not support Safari browser on Mac, but the Safari browser on PC can load.

3. xap file Call path problem: When calling XAP file in SharePoint development code, use the relative path of xap file (relative path), because one day you extend the current Web application to other areas You will use a different URL to access your web, and if you are using full path, your Silverlight WebPart will inevitably fail to load because of a change in the URL.

4. xap file Deployment location problem: As for how to deploy your XAP file, there are two common options, one is to create a document Library on your SharePoint site and then store your XAP file there. The other is to deploy to the "ClientBin" directory of "layouts", the benefit of which is to make it easier to operate on this location in the VS2010 environment.

5, WCF and Silverlight integration issues: In the combination of WCF proxy generation and Silverlight, when the WCF service is upgraded, you want to further upgrade your Silverlight project to this WCF Service Reference (Reference), and at this point you will find that proxy generation failed and the proxy classes could not be created in the project. Try to resolve this problem by reflecting the WCF service already deployed in your SharePoint site and modifying the Web.config settings.