Search Results for

# Upgrade Log

This page records the upgrade-facing status of the current AjaxUploader 5.0 Web Forms build.

It is meant for teams moving from older `CuteWebUI` projects to the current `AjaxUploader` codebase.

## Current v5.0 baseline

- `AjaxUploader.dll` is the main Web Forms assembly.
- JavaScript and CSS are embedded in `AjaxUploader.dll` and served through `ajaxupload.axd`.
- The main native controls are AjaxFileUpload, AjaxAttachments, and AjaxDropZone.
- The `CuteWebUI` compatibility namespace is still shipped for upgrade scenarios.
- Local development on `localhost`, `127.0.0.1`, and `::1` bypasses license detection.
- The v5 license file name is `ajaxuploader5.lic`.

## Upgrade-ready areas

Area | Current status | Upgrade impact
--- | --- | ---
Main upload runtime | Ready | Uses the current HTML5 client/runtime instead of old browser plugins.
Embedded resources | Ready | Separate published JS/CSS files are not required for Web Forms deployments.
Web Forms handler | Ready | Uploads, chunks, resources, and postback synchronization flow through `ajaxupload.axd`.
`CuteWebUI` compatibility namespace | Ready | Older markup and code-behind can keep compiling while pages are modernized gradually.
Legacy attachment model | Ready | `UploadAttachments`, `AttachmentItem`, and related events/providers are available.
Local development licensing | Ready | Localhost development no longer requires a license file lookup.
API/class reference docs | Ready | Generated API pages and handwritten migration guides are published under `/document/`.

## Important behavior changes

### HTML5 runtime replaces plugin-era behavior

AjaxUploader 5.0 is not trying to revive the old Flash or Silverlight runtime. Compatibility properties such as `UploadType`, `FlashLoadMode`, and related settings are preserved for source compatibility, but the active runtime is HTML5-based.

### Native v5 controls are cleaner than legacy wrappers

The native controls under `AjaxUploader.Controls` are intentionally simpler than the full legacy `CuteWebUI` object model.

That means:

- AjaxAttachments is lighter than legacy `UploadAttachments`
- `UploadedFileGuids` is the main native postback value
- richer legacy item/event behavior is preserved mainly in the compatibility layer

### `UploadPersistedFile` remains a compatibility-first concept

There is no direct native v5 control that exactly replaces UploadPersistedFile.

For upgraded pages, keeping UploadPersistedFile is still the simplest path. For new pages, build the same workflow explicitly on top of AjaxFileUpload.

## Practical upgrade notes

### Assembly strategy

For a normal v5 Web Forms application:

- deploy `AjaxUploader.dll`
- register the `AjaxUploader.Controls` namespace

For an older project that still depends on the old assembly name:

- keep `AjaxUploader.dll`
- add the legacy assembly only when the old assembly identity is still required at runtime

### Markup strategy

The safest path is:

1. keep existing `CuteWebUI` markup working first
2. verify uploads and postback processing
3. modernize page-by-page to the native `AjaxUploader.Controls.*` controls only when convenient

### Validation strategy

After upgrading a page, test these flows explicitly:

1. upload completes on the client
2. hidden field or GUID state reaches the next postback
3. server-side file processing can read the uploaded file by GUID
4. remove/delete behavior still matches the original page intent
5. deployed environment license file is found outside localhost

## Related guides

- Migrating From 4.x
- Legacy To v5 Map
- Legacy Uploader
- Legacy UploadAttachments
- Legacy UploadPersistedFile
- Deployment And Licensing