According to the statement in sivlerlight3:
In Visual Studio, you can add a resource file to a Silverlight project and set its"Generate operation"Value to configure these resource files for deployment. You can use the following generation operations for resource files in the Silverlight project:
Resources: This generation operation will embed the file into the projectProgramSet. You can use this option for applications and library projects, and deploy these assembly inside or outside the application package.
Content: This generation operation will include the file in the application package without embedding it in the project assembly. Use this option to use the resource files shared by multiple assembly in the package.
None: This generation operation does not include files in application packages or datasets. Use this option to search resource files as needed. Usually deploy on-demand files in the same location as the server where the application package is located.
However, when you select "content" to generate a Silverlight class library project, the resource file is neither embedded in the project assembly nor included in the application package.
Therefore, it is not suitable to set the resource file to "content" in the Silverlight class library project to share resource files for multiple projects. Select the default "resource" generation operation "/Assemblyshortname; Component/Resourcelocation "format URI reference resource file (For example, "/silverlightlibraryassembly; component/image.png ").
Note that the component is a keyword, and spaces are not allowed between the component and the semicolon.