You can view PDFs, Office files, CAD drawings, email, and images in the browser without installing legacy plugins. For Windows-based .NET applications, Doconut Viewer provides backend document processing while users remain inside the business application.

Modern plugin-free document viewing in a Windows browser application

In the next sections we’ll explore why removing legacy plugins matters, outline an ASP.NET Core integration workflow, and discuss drag-and-drop uploads and Blazor integration without relying on unverified SDK code.

Zero Plugins: Why They’re a Game‑Changer for .NET Web Apps

Eliminate the “install‑first” friction

Traditional viewers cling to ActiveX, Java, or Flash. Those old‑school techs demand permission, trigger security alerts, and often break on modern browsers. Doconut App sidesteps all that by rendering documents entirely in HTML5/Canvas. The result? A one‑click experience: click a link or drop a file, and the content appears instantly—no downloads, no prompts, no IT tickets.

Keep the browser sandbox intact

Since no external plug‑ins load, the browser’s sandbox stays untouched. That preserves the security guarantees enterprises rely on, especially when confidential PDFs or CAD drawings travel across the intranet. Doconut App adds SSL upload and AES‑256 storage, but the zero‑plugin core is what keeps the page from ever asking for elevated privileges.

Future‑proof across browsers and devices

HTML5 is the web’s universal language. As browsers evolve, they keep supporting the standards Doconut App uses, while legacy plug‑ins fade away. Whether a user is on Chrome, Edge, Safari, or a mobile WebView, the viewer behaves the same—no “plug‑in missing” warnings, no version‑specific workarounds.

Embedding Doconut App’s Plugin‑Free Viewer in ASP.NET Core

To integrate the viewer, generate a secure, temporary URL for the file on the server and pass it to the client‑side script. The server streams the encrypted file over HTTPS; the client‑side JavaScript provided by Doconut App renders it inside a <div> element.

Server‑side workflow (conceptual)

Receive a request for a document.
Retrieve the file from your storage (SQL, Blob, etc.).
Create a time‑limited, signed URL that points to the encrypted file.
Return that URL to the Razor view.

Razor view (conceptual)

Keep the view responsible for layout and authorized viewer state, while the server retrieves and processes the document. Use only the client resources and initialization sequence documented for the installed Doconut version.

When the page loads, the script looks for the data-doc-url attribute, fetches the encrypted file via HTTPS, decrypts it in memory, and paints the document on a canvas. No ActiveX, Java, or Flash—just pure HTML5.

Why this matters

Zero plugins: The only external asset is a lightweight JavaScript bundle from Doconut App.
Security baked in: The URL is time‑limited and signed, so nobody can reuse it.
Performance: The viewer streams only the bytes needed for the current viewport, so even massive DWG or PDF files appear quickly.

Rendering Supported Formats Without Plugins

Doconut App’s engine natively understands more than 50 source formats—including PDF, DOCX, XLSX, PPTX, DWG, DXF, PNG, JPEG, and many others. Because the engine works directly in the browser, there is no need for separate server‑side conversion services. The viewer detects the file type and renders it with pixel‑perfect fidelity, delivering a true plugin‑free experience.

Drag‑and‑Drop Upload with Instant, Plugin‑Free Rendering

Enterprises love letting users preview files on the fly. With Doconut App, you can add a drag‑and‑drop zone that uploads a document, generates a secure view URL, and displays the content without any plug‑in. The whole cycle stays inside your .NET back‑end, preserving compliance and audit trails.

Client‑side flow (conceptual)

User drags a file onto a designated area.
JavaScript sends the file to an ASP.NET Core endpoint.
The endpoint stores the file securely and returns a signed view URL.
The page injects a <div> with data‑doc‑url pointing to that URL.
Doconut App’s script renders the document instantly.

Because rendering happens entirely in the browser, there’s no heavyweight conversion service required on the server; Doconut App handles format decoding client‑side.

Consistent Viewing in Windows-Based Workflows

A browser viewer can provide a consistent entry point for users of an internal Windows application without requiring separate desktop document programs. Teams should test supported browsers, screen sizes, input methods, document complexity, and accessibility requirements rather than assuming identical behavior in every environment.

Extending the Viewer with Blazor – Keep Everything Inside Your .NET Ecosystem

If your team prefers a component‑centric approach, you can wrap Doconut App’s JavaScript viewer inside a Blazor WebAssembly component. This lets you stay within the .NET world while still delivering a zero‑plugin experience.

Blazor component outline (conceptual)

Inject a service that can generate a secure view URL for a given file ID.
On initialization, request the URL from the service.
After the component renders, initialize the viewer using the supported integration API for the installed Doconut version.

The Blazor component can coordinate viewer state while the backend remains responsible for document access and processing. This keeps the workflow inside the .NET application without publishing assumptions about a global JavaScript API.

Key Takeaways

Zero plugins eliminate installation friction, security warnings, and compatibility headaches.
Doconut App renders PDF, Office, CAD, and 50+ image formats directly in HTML5 Canvas.
Integration is straightforward: generate a secure view URL on the server and let the client‑side script paint the document.
Drag‑and‑drop upload + instant preview keeps users in the flow, all while staying plugin‑free.
The viewer works identically on desktop, tablet, and mobile because it relies on web standards, not legacy plug‑ins.
Blazor developers can encapsulate the viewer in a native .NET component without sacrificing the zero‑plugin advantage.
Security is reinforced by SSL upload, AES‑256 storage, and time‑limited URLs—plug‑ins never get a chance to expose vulnerabilities.

Common Questions

Q: Do I need to install anything on the client machines?
A: No. The Doconut App viewer runs entirely in the browser using HTML5 and JavaScript. Users only need a modern browser—no ActiveX, Java, or Flash installations are required.

Q: How does Doconut App handle large files?
A: The engine streams only the portions needed for the current viewport, so even hefty PDFs or DWG drawings load quickly. It also supports pagination, letting users jump to a specific page without re‑loading the whole document.

Get Started with Doconut App Today

Ready to eliminate legacy plugins from your Windows-based .NET application? Evaluate the Doconut SDK with the browsers, document formats, and workloads used by your organization.