Scribd
Upload
4 views

complete-reference-vb_net_81

Uploaded by

khalid
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
4 views

complete-reference-vb_net_81

Uploaded by

khalid
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Windows Forms

tablet, on the other side of the galaxy, on a console, or in another reality, without affecting the business logic
in any way whatsoever.

This disconnection is exactly how ASP.NET applications and rich−client applications will work as we move
into mainstream .NET development. All it takes to move a desktop application to the Internet is to drop the
form−based UI running on the client, and replace it with a Web form running on Internet Explorer.

The separation of the two application "domains" allows an effective development team to keep its best UI
people working on the front end while the logic and objects in the operational side of the application can be
worked on by the best class and object designers and code construction workers. As long as the "back−end"
developers understand that they are creating classes and objects that clients' code will "hook" into, you can
achieve a highly cohesive and productive software development workforce that lets developers that have an
artistic flair do a lot more that just screen painting.

There is no longer an excuse not to delegate properly with Visual Basic .NET and the power of the .NET
Framework. There is no excuse not to extend specialized and generic collections of classes with inheritance,
and there is no excuse not to delegate and use the power of polymorphism with native interfaces and
delegates.

A Windows forms program can be a stand−alone executable or exist as the client portion of a multitiered
system. There are various ways of connecting to the back−end logic, and the most cutting−edge method is via
Web services technology over HTTP. The server typically can be connected to a database, a mail server, or
any other collection of objects you care to call "server." The Windows forms technology is such that your new
featherweight classes can act as the UI to a powerful, data−enabled system that leverages the rich UI of a
client application with the advanced processing of an application server. To encapsulate this is a single
utterance: "The Web is dead, long live the Web."

Windows Forms
The Windows Forms technology is the new UI solution for the .NET Framework. All UI elements, such as
forms and visual input, output, and presentation components, extend a hierarchy of classes found in the
System.Windows.Forms namespace. You can use the forms classes and controls classes as is, or derive from
them to create your own UI and visual controls and components. The Windows forms are an ideal OOP
solution for creating rich UIs for local workstation clients, or as thin UIs developed for multitier distributed
solutions.

Windows−based UIs are typically cast in the following three styles:

• Single document interface (SDI) This is the UI that only opens a single document, such as Notepad
or WordPad or Outlook, which opens e−mails. You first have to close the current document before
you can open a new one. You can use the SDI application for simple document editors, various
utilities, and applications that do not need to work with multiple open forms.
• Multiple document interface (MDI) This UI contains numerous forms that encapsulate documents,
database input fields, grids, drawing areas, and various layouts and components. You can open new
forms in the UI as you need them. You do not need to close forms before opening new ones. Forms
inside the main form are enumerated into the Window menu for easy management and access. A good
example of the MDI application is Microsoft Word.
• Explorer−style interface This UI is an SDI application that is split into two panes inside a single
parent form. The left pane provides access to a tree of items, such as the so−called "cool" bar or some
other type of collection. The right pane provides the details of the node selected from the tree. A good

565

You might also like