Windows Forms

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
This API is a part of .NET Framework 3.0

Windows Forms (WinForms) is the name given to a graphical (GUI) class library included as a part of Microsoft .NET Framework,[1] providing a platform to write rich client applications for desktop, laptop, and tablet PCs.[2] While it is seen as a replacement for the earlier and more complex C++ based Microsoft Foundation Class Library, it does not offer a comparable paradigm[3] and only acts as a platform for the user interface tier in a multi-tier solution.[4]

Architecture

A Windows Forms application is an event-driven application supported by Microsoft's .NET Framework. Unlike a batch program, it spends most of its time simply waiting for the user to do something, such as fill in a text box or click a button.

Windows Forms provides access to native Windows User Interface Common Controls by wrapping the extant Windows API in managed code.[5] With the help of Windows Forms, the .NET Framework provides a more comprehensive abstraction above the Win32 API than Visual Basic or MFC did.[6]

Features

All visual elements in the Windows Forms class library derive from the Control class. This provides a minimal functionality of a user interface element such as location, size, color, font, text, as well as common events like click and drag/drop. The Control class also has docking support to let a control rearrange its position under its parent. The Microsoft Active Accessibility support in the Control class also helps impaired users to use Windows Forms better.[7]

Besides providing access to native Windows controls like button, textbox, checkbox and listview, Windows Forms added its own controls for ActiveX hosting, layout arrangement, validation and rich data binding. Those controls are rendered using GDI+.[7]

History and future

Just like Abstract Window Toolkit (AWT), the equivalent Java API, Windows Forms was an early and easy way to provide graphical user interface components to the .NET Framework. Windows Forms is built on the existing Windows API and some controls merely wrap underlying Windows components.[8]

Windows Forms provides a cross-platform way to design graphical user interfaces[citation needed]. However Windows Forms is mainly a wrapper around the Windows API, and some of the methods allow direct access to Win32 callbacks, which are not available in non-Windows platforms.[8]

In .Net 2.0, Windows Forms gained richer layout controls, office 2003 style toolstrip controls, multithreading component, richer design-time and data binding support as well as ClickOnce for web-based deployment[9][10]

With the release of .NET 3.0, Microsoft released a second API for rendering GUIs: Windows Presentation Foundation (WPF) based on DirectX,[11] together with a GUI declarative language called XAML. However, even though both Windows Forms and WPF offer comparable functionality, Windows Forms has not necessarily been superseded by WPF, but is simply another tool for Windows desktop application that will continue to exist parallel to WPF.[12]

During a Q and A session at the Build 2014 Conference, Microsoft explained that Windows Forms was under maintenance mode, with no new features being added, but bugs found will still be fixed.[13] Most recently, improved high-DPI support for various Windows Forms controls was introduced in updates to .NET Framework version 4.5.[14]

Alternative implementation

Mono is a project led by Xamarin (formerly by Ximian, then Novell) to create an Ecma standard compliant .NET compatible set of tools.

Mono's support for System.Windows.Forms as of .NET 2.0 is announced as complete;[15] also System.Windows.Forms 2.0 works natively on Mac OS X.[16] However, Windows.Forms is not actively developed on Mono,[17] and full compatibility with .NET is not achieved and is not possible, because Windows Forms is mainly a wrapper around the Windows API, and some of the methods allow direct access to Win32 callbacks, which are not available in platforms other than Windows.[8]

See also

References

  1. ↑ Windows Forms Programming in C# by Chris Sells, Addison-Wesley Professional; 1st edition (September 6, 2003) p xxxviiii
  2. ↑ Design and Implementation Guidelines for Web Clients by Microsoft Pattern and Practices. Microsoft (November 2003) https://msdn.microsoft.com/en-us/library/ff647339.aspx
  3. ↑ Appendix B. Moving from MFC, Windows Forms 2.0 Programming By Chris Sells, Michael Weinhardt. Addison-Wesley Professional; 2nd edition (May 16, 2006)
  4. ↑ Introduction to Windows Forms (Visual Studio 2003 documentation), Microsoft 2003,https://msdn.microsoft.com/en-us/library/aa983655(v=vs.71).aspx
  5. ↑ C# 4.0 Unleashed By Bart De Smet. Sams Publishing, Jan 4, 2011 Chapter 5 [1]
  6. ↑ NET Windows Forms in a Nutshell By Ian Griffiths, Matthew Adams O'Reilly Media (March 2003). p4
  7. ↑ 7.0 7.1 NET Windows Forms in a Nutshell By Ian Griffiths, Matthew Adams O'Reilly Media (March 2003). p27-53
  8. ↑ 8.0 8.1 8.2 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Appendix A. What s New in Windows Forms 2.0, Windows Forms 2.0 Programming By Chris Sells, Michael Weinhardt. Addison-Wesley Professional; 2nd edition (May 16, 2006)
  10. ↑ Data Binding with Windows Forms 2.0: Programming Smart Client Data Applications with .NET by Brian Noyes, Addison-Wesley Professional; 1st edition (January 12, 2006), Preface
  11. ↑ DirectX, not GDI+, Pro WPF and Silverlight MVVM: Effective Application Development with Model By Gary Hall, Apress; 2010 edition (December 27, 2010). p2
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Windows_Forms&oldid=1727999"