v4 compatibility demos

These pages are ports of the AjaxUploader 4.0 sample set, running on AjaxUploader 5. The markup, the event signatures and the client-side script are the v4 originals - only the DLL underneath changed. They exist to prove an upgraded v4 project keeps working, and to catch it in the build if that stops being true.

Upgrading from 4.x? These pages are the shortest answer to "will my code still run". Each one calls out the compatibility defect it covers, so if something misbehaves you can tell immediately whether it is your page or the control.

Simple Upload with Progress The baseline: <CuteWebUI:Uploader>, ValidateOption, and a FileUploaded handler with the v4 signature.
Selecting Multiple Files MultipleFilesUpload, one FileUploaded per file, and the automatic postback v4 pages rely on.
Multiple Files Upload (attachments list) Exercises the FileValidating and UploadCompleted events, and the MaxFilesLimit that was previously ignored.
Upload Validation DialogFilter file-type restriction and the per-control message properties, both inert before 5.3.2.
Start Uploading Manually The v4 client-side API: getqueuecount(), startupload() and CuteWebUI_AjaxUploader_OnPostback().
Your Own Upload Button InsertButtonID binding a page-rendered button as the browse control — inert before 5.3.9.
Large File Upload Chunked transfer and cross-session resume behind unchanged v4 markup.
Move a File Between Uploaders args.OpenStream() feeding the server-side Upload(size, name, stream) overload.
Persisted File Upload UploadPersistedFile and the nine members it lost when the v4 inheritance chain was broken.

What these cover

Every page above failed in some way on AjaxUploader 5.3.1 or earlier - some at compile time, some silently at runtime. The silent ones are the reason this folder exists: a page that renders and uploads can still be ignoring your file-count limit, your file-type restriction or your translated messages.