More and more Silverlight applications are applied to the web development environment, which is no exception in Sharepoint. The following are some notes about using Silverlight in sharepoint2010:
1. IE version problem: Silverlight xap files cannot be loaded in 64-bit ie. Therefore, use 32-bit IE to load.
2. Safari support problem: Silverlight webpart does not support safari on Mac, but can be loaded by Safari on PC.
3. xap file call path: Developed in SharePointCodeWhen calling the xap file, you must use the relative path (relative path) of the xap file, you will use different URLs to access your web. If you use full path, your Silverlight webpart will inevitably fail to be loaded due to URL changes.
4. xap file deployment location: There are two common options for how to deploy your xap file. One is to create a document library on your SharePoint website, then store your xap file there. Another method is to deploy it to the "clientbin" Directory of "layouts". The advantage of this method is that it is easy to operate on this location in the vs2010 environment.
5. Combination of WCF and Silverlight: When the combination of WCF proxy generation and Silverlight appears, after the WCF Service is upgraded, if you want to further upgrade the reference of this WCF Service in the Silverlight project, you will find that proxy generation fails and proxy classes cannot be created in the project. Try to solve this problem by reflecting the WCF Service deployed on your SharePoint website and modifying the settings of Web. config.