Classic integration

Use this section when an existing .NET 6 application still hosts Doconut through DocImage.axd, constructs Viewer manually, or copies the viewer scripts into the application. That architecture remains documented for customers who have not migrated.

Identify the classic integration

The package name alone is not enough. Both generations can use Doconut.NET6. The application is using the classic integration when it contains one or more of these signatures:

app.MapWhen(
    context => context.Request.Path.ToString().EndsWith("DocImage.axd"),
    branch => branch.UseDoconut(new DoconutOptions()));

var viewer = new Viewer(_cache, _accessor, licenseFilePath);
var token = viewer.OpenDocument(path, config, documentOptions);

Viewer.DoconutLicense(licenseStream);
Viewer.SetLicensePlugin(pluginLicenseStream);

Classic pages also commonly load application-managed copies of:

docViewer.js
documentLinks.js
docViewer.UI.js

The current integration is instead identified by AddDoconut(), UseDoconutResources(), UseDoconut(), an injected Viewer, and OpenDocumentAsync().

Open the preserved manual

The translated historic manual remains at Legacy .NET 6 setup. Its URL has not been redirected or replaced, because it describes a real integration generation that existing applications still use.

Do not combine snippets from that manual with the current AddDoconut() documentation. Viewer construction, middleware routing, licenses, resources, and session ownership are different.

Plan a migration

Use Migrate from the classic .NET 6 integration for the verified mapping from manual construction and synchronous document opening to DI, current middleware, async sessions, generated resources, and capability-gated plugins.

Keep the classic deployment intact until the current application passes its document, license, Search, Annotation, Converter, DICOM, security, and rollback tests.