This documentation is for the old version. Go to the latest Upload Suite docs

Installation and Deployment Notes

This topic provides instructions on how to install and uninstall Image Uploader Flash SDK on the developer machine. Besides, it describes files which should be deployed with an application which uses Aurigma Image Uploader Flash 7.2.9.

Installation

Download Image Uploader Flash SDK from http://www.aurigma.com/downloads/upload-suite location. Here the SDK is available in the following packages:

  • ImageUploaderFlash.msi, Windows-only installer
  • ImageUploaderFlashNoSetup.zip, ZIP archive
Then run this file and follow the wizard steps. During one of these steps you specify the folder where to install all Image Uploader Flash SDK files. Typically, this is C:\Program Files\Aurigma\Image Uploader Flash 7.2.9\. When the installation is completed you get a number of folders and files organized in the following structure:
/Image Uploader Flash 7.2.9
	/ASP.NET
		/Binaries
			/Aurigma.ImageUploaderFlash.dll
		/Samples_ImageUploaderFlashAspNet
		/Samples_ImageUploaderFlashJavaScript
	/PHP
		/PHPClasses
			/ImageUploaderFlashPHP
		/Samples_ImageUploaderFlashJavaScript
		/Samples_ImageUploaderFlashPHP
	/RequestEvaluationKey
	/Scripts	
	/Themes
	ImageUploaderFlash.chm
Note

There is no need to install Image Uploader Flash SDK on a server where you are going to run your application. Image Uploader Flash SDK is necessary on the developer machine only.

Uninstallation

To uninstall Image Uploader Flash SDK open Control Panel, click Programs and Features, then select Aurigma Image Uploader Flash 7.2.9 and click Uninstall. After that click Yes, and follow the wizard instructions.

Files to be Deployed

Image Uploader Flash SDK contains many files and folders, including Image Uploader Flash itself, special wrappers, demo application sources, and documentation. Of course, you do not need to copy all these files to your production server. The files to be moved to production server depend on a way used to embed Image Uploader Flash into your web application. There are three ways:

Image Uploader Flash ASP.NET

Image Uploader Flash ASP.NET enables ASP.NET developers to use Image Uploader Flash in a straight-forward way just as a common server control. See details in the Quick Start with Image Uploader Flash ASP.NET topic. If you use this way you need to copy the Aurigma.ImageUploaderFlash.dll file to the /bin folder of your web application.

Image Uploader Flash PHP

Image Uploader Flash PHP is a collection of classes which implement nearly the same functionality as the ASP.NET wrapper. Read more in the Quick Start with Image Uploader Flash PHP topic. If you use Image Uploader Flash PHP in your application you need to deploy the /ImageUploaderFlashPHP folder along with other files.

Image Uploader Flash JavaScript

Image Uploader Flash JavaScript includes a special API which is a base for both Image Uploader Flash ASP.NET and Image Uploader Flash PHP. To learn more about this wrapper read the Quick Start with Image Uploader Flash JavaScript topic first. All the files you need to deploy when using Image Uploader Flash JavaScript are located in the /Scripts folder.

Note

It is recommended to use minified versions of Image Uploader Flash JavaScript scripts in production environment in order to preserve bandwidth. These files support the same functions as usual Image Uploader Flash JavaScript, but have been optimized in size. The minified versions contain .min.js in their filenames.

Configuring Permissions

When deploying an application which uses Image Uploader Flash do not forget to set enough permissions to the folder you save files to:

  • On Windows NT/2000/XP you should grant the modify permission to the Internet guest user (IUSR_<machinename>).
  • On Windows 2003 Server you should grant the modify permission to the NETWORK SERVICE group.
  • On Windows Vista/2008 Server/7 you should grant the modify permission to the account your site application pool is running under, Network Service by default.
  • For *NIX systems you should specify read and write permissions.

See Also

Manual