This article describes how to use stand-alone versions of ActiveX control and Java applet as well as custom embedding scripts with Image Uploader ASP.NET control. It may be useful when you deploy a private-label version of Image Uploader or upgrade .cab and .jar files obtained from Aurigma without updating the ASP.NET control itself. If, however, you deploy Image Uploader using embedding scripts you should deploy a private-label version in the way described in the How to Use Private-label Versions topic.
Walk through the following steps to configure the ASP.NET control to launch stand-alone or private-label version of Image Uploader.
All the information you need to specify using these properties will be provided to you by Aurigma. If some parameters were not sent you should use default values.
The code sample below demonstrates how to implement this.
<cc1:ImageUploader ID="ImageUploader1" runat="server" height="400" width="600" ScriptsDirectory="MyUploader" ActiveXControlCabFileName="MyUploader.cab" JavaAppletJarFileName="MyUploader.jar" ActiveXControlVersion="6,0,2,0" JavaAppletVersion="18.104.22.168" ActiveXControlClassId="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" ActiveXControlProgId="MyCompany.MyUploader"; JavaAppletClassName="com.mycompany.myuploader.MyUploader.class" ActiveXControlUseCustomCodeBase="True" JavaAppletUseCustomCodeBase="True"> </cc1:ImageUploader>
If you use other Image Uploader-related classes (ShellComboBox, Thumbnail, and UploadPane) do not forget to perform the steps listed above for each class using their own CLSID, PROGID, and class name values. These values should be obtained from Aurigma too.
In the case when you need to use your custom Image Uploader
embedding scripts you should put them to the folder specified with the
and set IUEmbedScriptUseCustomCodeBase property to
When you customize Image Uploader embedding scripts you should not rename them, otherwise it will not be possible to use these scripts with Image Uploader ASP.NET control.