The licensing of the component uses
Visual Studio’s standard licensing approach for the components. It is based on
the use of licenses.licx files. For more information, please see here: http://helpcenter.perpetuumsoft.com/KB/a262/licenseslicx-file.aspx
The general approach is as follows:
when compiling a project in Visual Studio for all the components included into
the licenses.licx which are found on the machine where the compilation is
performed, all found licenses will be embedded into the assembly.
In case of Silverlight Viewer for
Reporting Services of 3.0+ versions, two components are licensed and both of
them are on the server side (where the WCF service is defined). To license the
product it is required to perform two steps:
If you do not have a licenses.licx file you need
to create it. This file is usually located in the Properties folder in case it
is a Web Application or it is located in the root folder if it is a Web Site.
Besides, Visual Studio does not allow to create files in the Properties folder.
So, you can create a simple text file in the root of the project and rename it
to licenses.licx. Then, it can be moved to the Properties folder.
Add the following lines to the licenses.licx file:
Please note that for 2.xxx product versions, only the first
component is used. The second one was introduced
only in the 3.xxx product versions. Thus, if you use 2.xxx version, you need to
delete the RemoteServiceProcessor
component description, otherwise, when compiling you will get an error that the
component is not found.
If you upgraded from 2.xxx to 3.xxx you need to reload license from our site and register it in the license manager instead of previous license. If you don't do that you will get the following information in the trial version window: 'ServiceProcessor requires 'MsReporting.Core option in license'.
Rebuild the project.
After that, the licenses should be embedded into the component. If this
did not happen, please see the following article: http://helpcenter.perpetuumsoft.com/KB/a346/solution-for-the-licensing-issues.aspx