Open WOW Designer to see some of the programs that we are going to convert. Open the project helowrld. Is a very simple program with just one form and a couple of controls. The “Click” event of the button contains some code to terminate the program. The “Close” event of the form contains the same code. Other events contain no code. The project “proprtes” contains two forms and some controls. As you can see, the “Create” event of the form contains some initializations and the “GetFocus” event contains just a DISPLAY statement that will be sent to the console window. Also, the “GetFocus” event of the smaller form contains a DISPLAY statement. By clicking the “Hide form” button, this code will be executed. Let’s close the WOW Designer and do the conversion to Visual Cobol. I simply add the WPJ files to the converter. There are no additional RM programs to include in the Visual Cobol solution, but I know that the samples look for the copybooks in the RM/COBOL directory. Therefore, I add that directory to the list. I leave the font substitution list unchanged. Winform fonts matching the WPF font will be left unchanged, the others will be changed to the “Global User Interface” font. Select the main program. It will be started when the launcher is run with no arguments. Enter the license string, set the source format to Fixed and leave the rest unchanged. Now we can start converting. We can see the progress in the log window. The conversion in finished. We can finally open Visual Cobol for Visual Studio and see the result of the conversion. A directory “WOWSAMPLES” has been created. SAMPLESLOADER contains a small program used to configure and launch the application. Here you can see the name of the main program that I selected in the conversion options. The SAMPLESSCREENS contains one directory for each WPJ project. Each directory contains one XAML file for each WOW form found in the WPJ project. Here you can see the “helowrld” form and here the forms in the “proprtes” project. Forms used in more than one WPJ will be created at root level to avoid duplications. The SAMPLES project contains all the COBOL source code. Again, you will find one directory for each WPJ project. The CBL contains the COBOL code needed to show the form or the forms. The WWS contains the definitions of the variables and the WPR contains the event code. Everything is left unchanged: the logic of your program does not change at all. And now we compile and run the solution. Ladies and gentlemen, Hello World! By changing the command line arguments we can run a different program. For example, “proprtes”. Run again and we see the “proprtes” program. This button will show the console window. Let’s play with the buttons to make sure that everything works as expected. Good, everything works. Now, you may want to change the converted programs. One of the first advantages is that your application can adapt itself to the current screen resolution. What the program needs to know is just the ideal resolution for your application. In this case, the samples were at their best at 800 by 600. All we have to do is add this line to configure the application. Run again. As you can see, the window now fills all the available vertical space. At higher resolutions, you won’t need to change anything: all the vertical available space will be used. What if we want to add another button? Just open the window you want to change, select one of the controls provided and set some properties. As you can see, the event code is still unchanged. Let’s add the “Click” event and jump to the code attached. Now the WPR contains the entry for the “Click” event of your button. Let’s add a DISPLAY just to have proof that it has actually been executed. The variables are still unchanged. When you are done with the changes of the user interface, click the “Generate WOW Source Code” and everything is updated. Run the program and the new button is there. Let’s make the console window visible. Click the button and the text appears. The code assistant is also useful for jumping to the code of the menu events. Just select a menu and the menu structure will be available. This is the code attached to the “Red” menu item. Of course, the program can be launched from a command prompt or a Windows shortcut. Just add the name of the program after the name of the executable and it will run. This is the program we have just seen in the IDE. The debugger is another great feature of Visual Cobol for Visual Studio. Let’s change the command line parameter to “wowcalc”. Open the source code. Of course, you can jump here from the window designer. Select a line and add a breakpoint. You can also go to the paragraph with the context menu. This is the code of the button “3”. Run the program, click some buttons, when the breakpoint is hit, the execution is paused and you can easily debug your program. The last program is very important because it shows that the converted programs will be able to use the printer just like before. Run the “ezmenu” program and print a report. As you can see, the default printer is used. In this case, the Bullzip PDF Printer. The list comes from a sample indexed file created by this program. We can add a record and print the report again. As you can see, the new record is there. Thank you for watching.