This topic discusses how to deploy ASP demo applications on your server.
To find information about how specific application works, see the Samples by Application topic.
ASP environment does not provide functionality required to process uploaded files by default. You should install third-party components. Below you will find several examples of upload components, which you can use.
|Dundas Upload||http://aspalliance.com/dundas/default.aspx||Supports buffering of uploaded data to the server drive. It is good for processing large uploads. The only disadvantage of this component is the absence of technical support.||Free|
|ABCUpload ASP||http://www.websupergoo.com/abcupload-1.htm||Commerical upload component. It can be obtained for free if you provide link to their website on your one.||$149 / Free with back link|
|Persists AspUpload||http://www.aspupload.com/||Yet another popular upload component.||$149|
None of these components are released by Aurigma. Aurigma does not give a warranty for reliability of the information given in the table above. This information is taken from official websites of the vendors of these components. It may be changed without Aurigma's knowledge and, therefore, it may become outdated.
To switch between different upload components:
Image Uploader can work with any HTTP-compliant ASP upload processing components. However, it is tested only with above four components. If you need to work with any other upload component, refer its documentation to write an appropriate upload script.
To get Server Imaging Sample sample working, you should install Aurigma Graphics Mill component. An evaluation version is available in this location:
Robust Upload Sample requires to calculate hash value based on the uploaded file. ASP does not provide built-in facility for this.
To be able to run this sample, use free hash generation ActiveX component developed by Aurigma. It is distributed along with Image Uploader SDK. Also, the component with the source code can be found in the following location:
If you get the error that says that ../ (a parent path) is disallowed in the Server.MapPath method, go to the Internet Information Services -> Web Site Properties -> Home Directory -> Configuration... -> Options and set the Enable Parent Path checkbox.
The most typical reason of this problem is server-side limitation for maximum POST request length. As usual it is specified to reduce risk of DoS attacks. If the request size exceeds specific value, it is considered as malicious and the upload is broken. As usual Image Uploader displays the following error message:
Upload failed (the connection was interrupted).
In IIS version 6.0 it is configured via the AspMaxRequestEntityAllowed element of the MetaBase.xml file, which stores miscellaneous IIS settings. By default this value is set to 200 KB.
To resolve the problem, follow these steps:
Make sure that MetaBase.xml file is writable. To do this, go to the properties of your server in IIS and set the Allow changes to MetaBase configuration while IIS is running checkbox.
If you have URLScan installed and still experience this problem, go through the following steps:
If you still experience problems with running demo applications, check out the Troubleshooting section. It contains information which may be helpful to resolve or diagnose them. Also, you can create support case or post a message on Image Uploader forum.