Installing ImageGear for Silverlight

Before installing ImageGear for Silverlight, make sure that your system complies with the requirements detailed in System Requirements.

1. Start the installer
   • From CD, insert the CD and auto-start should run setup.exe. If not you can manually run this from the CD. From setup.exe you can view the release notes or start the installer.
   • From Web, after the download finishes run the exe.
2. Click the "Next" button to continue past the welcome dialog.
3. Carefully read the information contained in the "License Agreement" form before making a decision to accept the terms of the agreement. Choose "I accept the license agreement" to accept the conditions outlined in the License Agreement and then click the "Next" button to continue the installation, or click "Cancel" to exit the installation process.
4. Once you click the "Next" button, the product "Select Features" form is displayed. In this form you can:
   • Choose the features and components of the selected product to install on your PC.
   • Get information about how much of your hard disk memory is required to install the product features that you have previously chosen.
   • Change the default installation directory.
5. When all these options are chosen, click the "Next" button to continue the installation process
6. At this point, the installer is ready to begin. Click the "Install" button to start the installation.
7. After the installation finishes, click "Finish" to close the installer.
8. Refer to the next section, Post-Installation Procedures, to make sure that your system is configured properly.

Post-Installation Procedures

ImageGear for Silverlight requires the following software to be installed and configured on a computer hosting Silverlight applications, including the ImageGear for Silverlight samples:

Microsoft ASP.NET IIS Registration

If IIS was installed after the .NET Framework 3.5, the service will fail, as IIS does not know how to handle .NET 3.5 applications. This does not prevent the sample from starting, as it does not use aspx.

If you installed IIS after the .NET Framework, you can set up the asp.net IIS registration with one of the following commands:

• Windows 32-bit:
  %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

• Windows 64-bit:
  %SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

You may also need to re-register the Windows Communication Foundation by running one of the following commands:

• Windows 32-bit:
  "%windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" /r /y

• Windows 64-bit:
  "%windir%\Microsoft.NET\Framework64\v3.0\Windows Communication Foundation\ServiceModelReg.exe" /r /y

Silverlight MIME Type

The Silverlight MIME type may need to be defined within the IIS server. To check that, go to the Control Panel, click Administrative Tools, and start the Internet Information Services (IIS) Manager.

• Windows Vista: Choose the "Default Web Site" and run MIME Types manager. Make sure the .XAP extension is in the list, if not, add it as application/x-silverlight-app.

• Windows XP: Right-click the "Default Web Site" and choose "Properties". Go to the HTTP Headers tab and Click File Types... Make sure the .XAP extension is in the list, if not, add it as application/x-silverlight-app.

ImageGear for Silverlight Samples HTTP Port

The samples and the SilverlightWebService URLs use default HTTP port 80 to communicate. If you use a different port for the web site from which the samples and the service are running, please make sure to change the samples URL files and webServiceUrl string used by ImGearLicense.SetService() call in the sample code (Page.xaml.cs) to explicitly specify the port number (by adding ':<port number>' after the hostname), and rebuild the samples. You may also need to clear the browser's cache.

Resolving Common Installation and Configuration Issues

A full installation of ImageGear for Silverlight requires that Microsoft .NET Framework 3.5 SP1 and Microsoft Silverlight 2.0 be installed. If .NET and/or Silverlight are not installed, the ImageGear installer will guide you through those installations, and will not continue installing ImageGear until .NET and Silverlight are installed.

When the installation is complete, you will be given the option to register ASP.NET and re-register WCF with IIS. While this might not be required on your machine, Accusoft recommends that you complete these steps. Doing so will cause no harm and may simplify any future troubleshooting. See Post-Installation Procedures for details.

This section identifies some common installation and configuration issues, and provides solutions to these issues.

Using ImageGear for Silverlight

Before you can use any ImageGear functionality, you need to call the ImageGear licensing API. When you evaluate the product or develop your application using ImageGear, you have to call the Set Solution Name API function: 

In C# applications, the call to SetSolutionName() method looks like this:

ImGearLicense.SetSolutionName("AccuSoft 5-44-17");

The ImageGear samples installed with the product already have this call included, so you can simply copy/paste this call from the source code of the samples. 

NOTE: The samples and the SilverlightWebService URLs use default HTTP port 80 to communicate. If you use a different port for the web site from which the samples and the service are running, please make sure to change the samples URL files and webServiceUrl string used by ImGearLicense.SetService() call in the sample code (Page.xaml.cs) to explicitly specify the port number (by adding ':<port number>' after the hostname), and rebuild the samples. You may also need to clear the browser's cache.

NOTE: ImageGear reads the license information from the registry. You have to obtain the product license (evaluation or development) using the AccuSoft License Manager (see "Installing and Distributing ImageGear" Chapter of the product documentation included in your package) in order for the product to work.

When you’re ready to deploy your application you will need to use all three licensing API calls.  Please refer to the product documentation for the details of how to use these calls. Please contact Accusoft Pegasus about obtaining a License Deployment Kit. It will explain additional steps (including the API calls) that you need to take to deploy your application.