If you have an existing AWT Java application you want to deploy under .NET, porting it is a sensible approach. But if you have an application built using Swing, you’ll most likely want to redevelop the GUI using .NET classes, for three main reasons:
J# does not provide support for Swing.
You can take advantage of the wide variety of GUI components that .NET offers.
Applications built using .NET classes can run much faster than their Java peers.
In this section, we’ll continue with the theme of the text editor. Specifically, rather than using JDK constructs, we’ll build an equivalent application using the .NET Framework. As you walk through the code, pay particular attention to areas where .NET development ...