WinForms to Web - Migrating desktop applications part 1

WinForms to Web - Migrating desktop applications part 1


This is the first article in a series of articles that describes the various migration options of desktop/smart client applications to the web available using Visual WebGui.

In order to discuss the migration process of legacy desktop applications to the web, we should first agree on 3 different types of desktop applications:

1. WinForms based desktop application (C#/VB.NET).
The UI layer is coded using .NET languages – the business can be .NET, COM+ or any other interop.

2. VB 6.0 based applications.
The UI layer is coded with VB 6.0.

3. Smart client or other desktop technologies (C++ MFC/ATL, Delphi, Java etc).
Any other smart client technology based applications.
This document describes the migration process of WinForms based desktop applications to the web using Visual WebGui.
WinForms based desktop applications


Normally, without Visual WebGui the migration process of a WinForms desktop application to the web will require a full re-engineering of the UI layer to fit the web architecture and capabilities.

If we take WinForms migration to ASP.NET for example using any AJAX 3rd party controls in order to provide a rich UI experience, we will have to consider:

1. Entirely new API.
2. Entirely new update approach.
3. Entirely new look & feel – or work hard to customize the UI to look the same.
4. Lighten the amount of data transferred to the client and presented at any given time to avoid severe latency.
5. Compromise on features list due to the web limitations.
6. Handling security holes created as a result of opening services consumed by client side AJAX and transferring business logics to the client.
Visual WebGui SDK is fully integrated with Visual Studio and provides the exact same API and set of tools/capabilities which are provided out-of-the-box with WinForms 1.0 and 2.0. This fact enables the native capability of simply copying any existing WinForms source code to a VWG project and providing a fully functional equivalent web application.

The Process

The basic 3 steps of migration (view a walkthrough tutorial):
1. Open a new Visual WebGui application.
2. Copy the code from your WinForms project into this new web application.
3. Replace any reference to WinForms API namespace (“System.Windows.Forms”) within the code to Visual WebGui API reference (“Gizmox.WebGUI.Forms”).
Any standard WinForms application which is using the 58 WinForms out-of-the-box controls will then compile and execute as a plain web application.
The outcome of this short process is an ASP.NET based solution in terms of deployment and runtime and has the following properties:
A. Deployment is copy & paste equivalent to an ASP.NET web site.
B. Server infrastructure requires an IIS and .NET CLR only.
C. The application can be consumed from any plain browser - no installation is made on the client.
D. Minor static and cached footprint on the client ~200kb of plain JS and HTML code due to the Empty Client concept.
E. Support for multiple presentation layers with the same code base (DHTML/Silverlight or Smart Client)
F. Maintain a single layer of code – no need to write or maintain JavaScript, HTML and services
G. Highly secured due to the Empty Client concept.
Considerations & Exceptions

There are 3 major setbacks you might have on the process which you can quantify in advance and estimate the amount of work that has to be done in order to migrate your application:

1. Minor differences between the VWG API and WinForms which are mainly caused by architecture differences.

2. The amount of 3rd party controls that are used in your application.
This section describes a situation of using some non-WinForms out-of-the-box controls (for example Infragistics or DevExpress controls etc). In those cases you can select the most suitable solution from the following 3 options:

a. Choose a similar control from the WinForms out-of-the-box, adjust your code to use it and then perform the migration process.

b. Select an equivalent 3rd party ASP.NET control (Infragistics, Telerik, DevExpress etc.) which provides the same functionality, wrap it by a click of a button in VWG and adjust your code to use it.

c. Write your own VWG custom control which will perfectly suit your needs and then adjust your code after the migration process to use this control.

3. Adjustments of a single user desktop application to a multiuser web environment. This section summarizes some of the major issues of transforming a single user application to a multiuser application sharing the same CPU, Memory space and other resources.

a. Thread safety – since a WinForms application can contain static members which are accessible to a single user, you should now consider one of the following:

i. Replacing those static members to a synchronized multi-thread safe data structures.
ii. Lock critical read/write sections to protect concurrent multi user access.
iii. Remove the statics and find instance or DB based solutions.

b. Memory load – in a desktop application, there might be places when the original consideration of the amount of memory in use was based on the assumption that the executing machine is local. therefore, many items are loaded to memory simultaneously without limitation.
Now, on a shared memory environment, when the server does the heavy lifting, the amount of memory consumed by each user will set the number of concurrent users that can be served by each server.

The following steps are recommended:

i. Consider loading items to memory on demand (keep only the headers and the identifiers in memory).
ii. Remove any large objects read to memory – for example, don’t save binary objects to memory, instead write the binary to the response stream directly to the client.
iii. Prefer DB based paging on entire prefaces and memory based paging. Visual WebGui provides mechanisms to enable it easily.


Migration of any WinForms application to the web using Visual WebGui has the following advantages:
1. In 3 simple steps you will be able to get very close to a working web application.
2. The effort you have to make in order to accomplish a fully functional web application is measurable.
3. The application can keep using the existing BL and DL layers, and only the UI is either migrated automatically or adjusted.


  • WinForms to Web - Migrating desktop applications part 1 (25380-25513-WinForms to Web - Migrating desktop applications part 1 (2).doc)
  • Comments

    No responses found. Be the first to comment...

  • Do not include your name, "with regards" etc in the comment. Write detailed comment, relevant to the topic.
  • No HTML formatting and links to other web sites are allowed.
  • This is a strictly moderated site. Absolutely no spam allowed.
  • Name: