VWG Advanced Migration

The following steps describe the advanced migration processes to go from Visual WebGUI to Wisej.NET

Unused Control Properties

Porting from WinForms to Wisej.NET is as easy as just replacing the namespaces from System.Windows.Forms to Wisej.Web, it's effortless as only a handful of changes are needed to compensate for moving to the Web.

The procedure is fairly similar for Visual WebGUI, there are a few modifications that you'll need to consider before attempting to open any Form or User Control in the designer.

As an example, Visual WebGUI controls have a list of properties that are not present in an equivalent Wisej.NET control, some of these properties are:

• ExcludeFromUniqueId

• NextFocusId

• PreviousFocusId

• PerformLayoutEnabled

• RenderCellPanelsAsText

• RowTemplate (DataGridView)

• RenderCellPanelsAsText (DataGridView)

These properties can be deleted as they do not serve a purpose with Wisej.NET, if perhaps these properties are needed, you can create a compatibility class, also called a shim class, that inherits from the base Wisej.NET control and add those unimplemented properties.

MessageBox handling

The MessageBox control in Wisej.NET has a different signature compared to Visual WebGUI

As an example, below you'll find how a MessageBox is shown with Visual WebGUI

MessageBox.Show("Your Message", "Your Caption", MessageBoxButtons.YesNo, MessageBoxIcon.Question, MessageBoxHandler, true);

While in Wisej.NET, it becomes:

MessageBox.Show("Your Message", "Your Caption", MessageBoxButtons.YesNo, MessageBoxIcon.Question, onclose: MessageBoxHandler);

With that in mind, an update to the MessageBoxHandler's method signature is required, otherwise, it will yield a compilation error

private void MessageBoxHandler(DialogResult result)
{
        //Your MessageBox Handling Code
}

Best Practices

In order to get the most out of Wisej.NET, there are a few alterations that are beneficial to the application's performance.

Professional services and turn-key migration solutions are available from the makers of Wisej.NET and a number of international partners. Get in touch! We have the knowledge, tools, and libraries to support you in the Porting Process.

Use ImageSource instead of Image Property

If your application has a lot of image resources, it would be much more beneficial to use the ImageSource property instead of the regular Image Property. The difference is that Wisej.NET directly uses the image file as opposed to having the server process it and then send it back to the client.

If you want to use custom Theme images or icons, you have to use the ImageSource property.

Example of using a Theme icon or image

this.pictureBox1.ImageSource = "icon-copy";

Example of using a local image from the Resource folder

this.pictureBox1.ImageSource = "resource.wx/Resources/some_image.png";

Controls sizing and responsiveness

One of the limitations that Visual WebGUI had was the lack of responsiveness, meaning that a control's size had to be always recalculated when the client gets resized.

Wisej.NET is responsive by nature, so you won't need to recalculate a control's position or size every time a client gets resized!