Legacy To v5 Map
This page is the quickest way to map older CuteWebUI usage to the current v5 Web Forms surface.
Control mapping
| 4.x style control | Closest v5 target | Notes |
|---|---|---|
CuteWebUI.Uploader |
AjaxFileUpload | Main upload control. Best native replacement for most upload pages. |
CuteWebUI.UploadAttachments |
AjaxAttachments | Best native replacement for compact attachment-list UI. |
CuteWebUI.UploadPersistedFile |
Keep UploadPersistedFile or build on AjaxFileUpload | There is no direct native one-file persisted wrapper in v5. |
DropZoneID or standalone drop behavior |
AjaxDropZone or AjaxFileUpload with built-in drop UI | Use the native drop zone control for drag-and-drop focused pages. |
CuteWebUI.Uploader to AjaxFileUpload
| Legacy member | Native v5 member | Notes |
|---|---|---|
InsertText |
ButtonText |
Same purpose. |
MultipleFilesUpload |
Multiple |
Enables multi-file selection. |
ManualStartUpload |
AutoUpload |
Inverse meaning. ManualStartUpload="true" becomes AutoUpload="false". |
ShowProgressBar |
ShowProgress |
Shows built-in progress UI. |
ShowQueueTable |
ShowQueue |
Shows built-in queue UI. |
MaxFilesLimit |
MaxFiles |
Limit the queue size. |
ValidateOption.AllowedFileExtensions |
Extensions |
Comma-separated extensions. |
ValidateOption.MaxSizeKB |
MaxSize |
v5 expects a string such as 10485760, 10MB, or 1GB. |
FileUploaded |
FileUploaded |
Same server-side event idea, but native args are FileUploadedEventArgs. |
UploadCompleted |
UploadCompleted |
Same batch-complete concept. |
UploadAttachments to AjaxAttachments
| Legacy member | Native v5 member | Notes |
|---|---|---|
InsertText |
ButtonText |
Same purpose. |
ShowRemoveButtons |
Removable |
Controls whether items can be removed from the client list. |
ShowFileIcons |
custom rendering | Native v5 does not reproduce the old attachment table visuals automatically. |
ShowTableHeader |
custom rendering | The native control is intentionally more compact. |
ValidateOption.AllowedFileExtensions |
Extensions |
Same idea. |
ValidateOption.MaxSizeKB |
MaxSize |
v5 accepts bytes or KB/MB/GB suffixes. |
Items |
UploadedFileGuids plus your own rendering |
The native control returns uploaded GUIDs, while the legacy wrapper preserves the richer item model. |
AttachmentAdded and related events |
OnClientChange plus postback processing |
Native AjaxAttachments is intentionally lighter on server-side item lifecycle events. |
UploadPersistedFile strategy
If the page already works with CuteWebUI.UploadPersistedFile, the simplest path is to keep using that compatibility control.
If you want a native v5 page instead:
- Use AjaxFileUpload.
- Store the latest uploaded GUID in a hidden field or server property.
- Persist the file explicitly during your form save logic.
Built-in compatibility aliases on AjaxFileUpload
The native v5 control already exposes several compatibility aliases, which can reduce rewrite work even after you switch away from CuteWebUI.
Alias on AjaxFileUpload |
Native target |
|---|---|
AllowMultiple |
Multiple |
AllowedExtensions |
Extensions |
MaxFileSize |
MaxSize |
MinFileSize |
MinSize |
EnableChunkedUpload |
Chunked |
EnableDropZone |
DropZone |
EnablePaste |
Paste |
EnableDuplicateCheck |
DetectDuplicates |
EnableImagePreview |
ShowThumbnails |
ConcurrentUploads |
Concurrent |
ParallelChunks |
Concurrent |
OnClientFileSelected |
OnClientSelect |
OnClientUploadComplete |
OnClientComplete |
Recommended decision rule
- If the page is old but stable, keep the
CuteWebUIcompatibility control first. - If you are rewriting the page anyway, move to the native
AjaxUploader.Controls.*controls. - If you only need a few renamed members, start with the native control and lean on its compatibility aliases where they already exist.