Modernizing Legacy WebForms & MVC Apps with Doconut
← Back to Blog••2 min read

Modernizing Legacy WebForms & MVC Apps with Doconut

The Legacy Application Dilemma

Many enterprises still rely on robust, mission-critical applications built on ASP.NET WebForms or older versions of MVC. While the backend logic remains solid, the frontend experience often suffers—especially when dealing with documents.

Legacy solutions typically rely on technologies that are now obsolete or problematic:

  • ActiveX Controls: Only work in Internet Explorer (which is retired).
  • Flash/Silverlight: Completely unsupported in modern browsers.
  • PDF Plugins: Require users to have Acrobat Reader installed and updated.

Doconut: The Bridge to Modernity

Doconut supports .NET Framework 4.7.2, .NET Standard 2.1, .NET 6, and .NET 8 packages, with integrations for Web Forms, MVC, ASP.NET Core, Razor Pages, and Blazor Server.

Seamless WebForms Integration

Integrating Doconut into a WebForms project is straightforward. You don't need to rewrite your entire UI.

  1. Add the Reference: Install the NuGet package.
  2. Add the Handler: Register the document handler in web.config.
  3. Embed the Script: Add the JavaScript viewer to your .aspx page.

Use the HTML5/JavaScript widget and server integration shown in the official sample for the Doconut package version you are deploying.

From Plugin-Hell to HTML5

By switching to Doconut, you immediately gain:

  • Mobile Browser Support: The viewer works in mobile browsers; Doconut does not provide native iOS or Android SDKs.
  • No Plugins: Users just open the page, and the document appears. Zero installation tickets for IT.
  • Modern Features: Add annotation, search, and zooming capabilities that old plugins never had.

Strategy: Upgrade vs. Rewrite

Complete rewrites of large legacy systems are risky and expensive. A "strangler fig" approach—upgrading specific components like the document viewer—offers high impact with low risk.

You can modernize the User Experience of viewing contracts, blueprints, and reports today, buying you time to plan a backend migration to .NET Core in the future. When migrating between supported .NET application models, review the package and integration documentation for the target runtime.

Don't let legacy tech hold your data hostage. Upgrade to Doconut and give your users the modern experience they expect.

#Legacy Migration#WebForms#MVC#Modernization#.NET Framework