The following peace of code contains a small project that demonstrates creating a simple download button using a gateway.

This code sample demonstrates a script component which is used to get a file name from the user. The script component combines both a client invocation usage and raising events to provide information about the user feedback.

This code sample demonstrates a simple application that has two registered forms which can be switched between.

This sample code shows how to switch the current UI culture in run time and to refresh the UI text.

This sample code demonstrate how to add support for the browser's Back/Forward/Refresh buttons.

This sample code demonstrates how to switch themes in runtime.

This code demonstrates how to switch the current main form to a different form.

This sample code demonstrates the ability to use the new FolderBrowserDialog to create custom browsing dialogs. In this case we have create a simple dialog that can select registry keys. This is just a sample to show how you populate the dialog with custom data. Because this control is by default implemented using the server folders which is not your average scenario this control has the ability to be customized to accommodate the customers needs.

The KeyFilter property is a new property that was added to control. Handling the KeyDown /KeyUp / KeyPress generates a callback on every key down which can be a great overhead if all you want is to handle a specific key down. That is way the new KeyFilter property was added. Basically it allows to define a filter which helps VWG generate callbacks only when you really need it. In the following sample code we have demonstrated the implementation of adding arrow behaviors to a set of text boxes which allows navigating between the fields.

This sample code demonstrates working with user controls to simulate frames.

This sample code demonstrates working with a background thread that can be monitored from the VWG UI. It is important to remember that ASP.NET limits the amount of non request threads by default to 20, but this can be a very nice solutions for long actions scenarios that can live within this limitation.

This sample code demonstrates how you can integrate printing capabilities into your application in a structured way.



The code presents the IPrintable interface which should be implemented by each control which can be printed within your rendered form. This interface defines the Print method that is responsible for rendering the desired form of HTML suitable for the control. Looping the IPrintable controls in the form and invoking Print() method on each of those controls provides a generic mechanism of rendering and printing the entire form as a unit.