Windows Forms: Difference between revisions

Revision as of 14:11, 14 November 2020

Latest revision as of 05:01, 5 June 2025

(48 intermediate revisions by 32 users not shown)

Line 1:

{{distinguish|Microsoft Forms}}

{{update|date=January 2023}}

{{short description|Graphical user interface software library}}

{{Infobox software

| name = Windows Forms (WinForms)

| screenshot = Screenshot of WinForms Designer as seen in Visual Studio 2019.png

| logo = WinForms Logo.png

| screenshot alt = Screenshot of Windows Forms designer as seen in [[Visual Studio 2019]].

| author = [[.NET Framework|.NET]]: [[Microsoft]],<br />[[Mono Framework|Mono]]: [[Ximian]]/[[Novell]]

| developer = [[.NET Foundation]]

| other_names = WinForms

| released = {{Start date and age|2002|02|13}}

| developer = [[.NET Foundation]]

| latest release version = v5.0.0-rtm.20520.1

| latest release date released = {{Start date and age|20202002|1002|2013}}

| latest release version = v5v8.0.0-rtm.20520.1

| latest release date = {{Start date and age|2023|11|14}}<ref>{{cite web|url=https://github.com/dotnet/winforms/releases/tag/v8.0.0|title=v8.0.0|date=2023-11-14|website=github.com|access-date=2023-11-21}}</ref>

| latest preview version =

| latest preview date =

| programming language = [[C Sharp (programming language)|C#]]

| operating system = [[Microsoft Windows]]

| platform = [[.NET Framework]], [[.NET]], [[Mono Core(software)|Mono]]

| genre = [[Software framework]], [[widget toolkit]]

| license = [[MIT License]]

| website = {{URL|https://docslearn.microsoft.com/en-us/dotnet/frameworkdesktop/winforms/}}

}}

'''Windows Forms''', (also known as '''WinForms)''', is a [[free and, open-source]] [[graphical user interface|graphical]] (GUI) [[Library (computing)|class library]] for building Windows desktop applications, included as a part of [[Microsoft]] [[.NET]], [[.NET Framework]] or [[Mono Framework(software)|Mono]],<ref>{{cite book|title=Windows Forms Programming in C#|last=Sells|first=Chris|publisher=Addison-Wesley Professional|edition=1st|date=September 6, 2003|page=xxxviiii}}</ref> providing a platform to write rich client applications for desktop, laptop, and tablet PCs.<ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/ff647339.aspx|title=Design and Implementation Guidelines for Web Clients by Microsoft Pattern and Practices|publisher=Microsoft|date=November 2003}}</ref> 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<ref>{{cite book|chapter=Appendix B|title=Moving from MFC, Windows Forms 2.0 Programming|last1=Sells|first1=Chris|last2=Weinhardt|first2=Michael|publisher=Addison-Wesley Professional|edition=2nd|date=May 16, 2006}}</ref> and only acts as a platform for the user interface tier in a [[Multitier architecture|multi-tier]] solution.<ref>{{cite web|title=Introduction to Windows Forms|type=Visual Studio 2003 documentation|publisher=Microsoft 2003|url=https://msdn.microsoft.com/en-us/library/aa983655(v=vs.71).aspx}}</ref>

At the [[Microsoft Connect]] event on December 4, 2018, [[Microsoft]] announced releasing Windows Forms as an open source project on [https://github.com/dotnet/winforms [GitHub]]. It is released under the [[MIT License]]. With this release, Windows Forms has become available for projects targeting the [[.NET Core]] framework. However, the framework is still available only on the Windows platform, and [[Mono Framework|Mono's]] incomplete implementation of WinFormsWindows Forms remains the only cross-platform implementation.<ref name="OpenSourcingGuiMartin">{{cite web |url=https://www.infoq.com/news/2018/12/msft-open-source-wpf-winforms | title=Microsoft Open Sources WPF, WinForms, and WinUI | last=Martin | first=Jeff | work=InfoQ | publisher= | date=4 December 2018| archive-url= | archive-date=2018-12-06|access-date=2018-12-06 }}</ref><ref name="OpenSourcingGuiHanselman">{{cite web |url=https://www.hanselman.com/blog/AnnouncingWPFWinFormsAndWinUIAreGoingOpenSource.aspx | title=Announcing WPF, WinForms, and WinUI are going Open Source | last=Hanselman | first=Scott | work= | publisher= | date=4 December 2018| archive-url= | archive-date=2018-12-06|access-date=2018-12-06 }}</ref>

== Architecture ==

[[File:DotNet3.0.svg|thumb|right|300px|This [[application programming interface|API]] is a part of [[.NET Framework]] 3.0]]

A ''Windows Forms application'' is an [[event-driven programming|event-driven application]] supported by Microsoft's [[.NET Framework]]. Unlike a [[batch processing|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 [[push-buttonButton (computing)|button]]. The code for the application can be written in a .NET programming language such as [[C Sharp (programming language)|C#]] or [[Visual Basic .NET|Visual Basic]].

Windows Forms provides access to native [[Windows USER|Windows User Interface]] Common Controls by wrapping the existent [[Windows API]] in [[managed code]].<ref>{{cite book|url=http://www.informit.com/articles/article.aspx?p=2048355&seqNum=4|title=C# 4.0 Unleashed|last=De Smet|first=Bart|publisher=Sams Publishing|date=January 4, 2011|chapter=Chapter 5}}</ref> With the help of Windows Forms, the .NET Framework provides a more comprehensive abstraction above the Win32 API than Visual Basic or MFC did.<ref>{{cite book|title=NET Windows Forms in a Nutshell|last1=Griffiths|first1=Ian|last2=Adams|first2=Matthew|publisher=O'Reilly Media|date=March 2003|page=4}}</ref>

Line 32 ⟶ 36:

== Features ==

All visual elements in the Windows Forms class library derive from the Control class. This provides the 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.<ref name="Griffiths2003">{{cite book|title=NET Windows Forms in a Nutshell|last1=Griffiths|first1=Ian|last2=Adams|first2=Matthew|publisher=O'Reilly Media|date=March 2003|pages=27–53}}</ref>

In Visual Studio, forms are created using [[drag-and-drop]] techniques. A tool is used to place controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have [[Attribute (computing)|attributes]] and [[Event handler|event handlers]] associated with them. Default values are provided when the control is created, but may be changed by the programmer. Many attribute values can be modified during run time based on user actions or changes in the environment, providing a dynamic application. For example, code can be inserted into the form resize event handler to reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text box, the program can automatically translate the case of the text being entered, or even prevent certain characters from being inserted.

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 [[Graphics Device Interface|GDI]]+.<ref name="Griffiths2003"/>

Line 42 ⟶ 48:

| quote= ''It is very unlikely that the implementation will ever implement everything needed for full compatibility with Windows.Forms. The reason is that Windows.Forms is not a complete toolkit, and to work around this problem some of the underlying Win32 foundation is exposed to the programmer in the form of exposing the Windows message handler''}}</ref> Some of the methods allow direct access to Win32 [[Callback (computer programming)|callbacks]], which are not available in non-Windows platforms.<ref name="monofaq-winform"/>

In .NET Framework 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.<ref>{{cite book|chapter=Appendix A. What s New in Windows Forms 2.0|title=Windows Forms 2.0 Programming|last1=Sells|first1=Chris|last2=Weinhardt|first2=Michael|publisher=Addison-Wesley Professional|edition=2nd|date=May 16, 2006}}</ref><ref>{{cite book|title=Data Binding with Windows Forms 2.0: Programming Smart Client Data Applications with .NET|url=https://archive.org/details/databindingwithw0000noye|url-access=registration|last=Noyes|first=Brian|publisher=Addison-Wesley Professional|edition=1st|date=January 12, 2006|chapter=Preface|isbn=978-81-317-4823-7 }}</ref>

With the release of .NET Framework 3.0, Microsoft released a second, parallel API for rendering GUIs: [[Windows Presentation Foundation]] (WPF) based on DirectX,<ref>{{cite book|section=DirectX, not GDI+|title=Pro WPF and Silverlight MVVM: Effective Application Development with Model|last=Hall|first=Gary|publisher=Apress|edition=2010|date=December 27, 2010|page=2}}</ref> together with a GUI declarative language called [[Extensible Application Markup Language|XAML]].<ref>{{cite web

| accessdateaccess-date = 2011-08-25

| last = Smith

| first = Josh

Line 57 ⟶ 63:

| first=Josh|last=Smith

| date=2007-09-05

| accessdateaccess-date=2008-07-26}}</ref><ref>{{cite web

| url=http://blogs.msdn.com/mharsh/archive/2004/09/20/231888.aspx

| title= WPF vs. Windows Forms

Line 63 ⟶ 69:

| quote=''If you’re targeting only Windows XP and Longhorn, Avalon is the way to go. But Windows Forms is still the only way to write managed UI that will run on Win 2K and below''

| date=2004-09-20

| accessdateaccess-date=2008-07-26}}</ref><ref>{{cite web

| url=http://www.longhorncorner.com/Blogs/BlogDetail.aspx?BlogId=660

| title= Future of Windows Forms and ASP.NET

| first=Mahesh|last=Chand

| date=2008-05-08

| accessdateaccess-date=2008-07-26}}</ref>-->

During a question-and-answer session at the [[Build (developer conference)|Build 2014]] Conference, Microsoft explained that Windows Forms was under maintenance mode, with no new features being added, but bugs found would still be fixed.<ref>{{cite web

Line 76 ⟶ 82:

| date=2014-04-03

| quote=''Windows Forms is continuing to be supported, but in maintenance mode. They will fix bugs as they are discovered, but new functionality is off the table''

| accessdateaccess-date=2014-04-21}}</ref> Most recently, improved high-DPI support for various Windows Forms controls was introduced in updates to .NET Framework version 4.5.<ref>{{Cite web|url = http://www.infoq.com/news/2014/05/DotNet-4-5-2|title = High DPI Improvements for Windows Forms in .NET 4.5.2|date = 2014-05-06|accessdateaccess-date = 2015-02-10|website = InfoQ|publisher = |last = Allen|first = Jonathan}}</ref>

==XAML Backwardsbackwards Compatibilitycompatibility with WinFormsWindows Forms==

For future development, Microsoft has succeeded WinFormsWindows Forms with a [[XAML]] -based GUI entry using Frameworksframeworks such as [[Windows Presentation Foundation|WPF]] and [[Universal Windows Platform|UWP]]. However, drag and drop placement of GUI components in a manner similar to WinFormsWindows Forms is still provided in XAML by replacing the root XAML element of the Page/Window with a "Canvas" UI-Control. When making this change, the user can build a window in a similar fashion as in WinFormsWindows Forms by directly dragging and dropping components using the Visual Studio GUI.

While XAML providedprovides drag and drop placement backwards compatibility through the Canvas Control, XAML Controls are only similar to WinFormWindows Forms Controls and are not 1one-to-1one backwards compatible. They perform similar functions and have a similar appearance, but the properties and methods are different enough to require remapping from one API to another.

== Alternative implementation ==

[[Mono (software)|Mono]] is a project led by [[Xamarin]] (formerly by [[Ximian]], then [[Novell]]) to create an [[Ecma International|Ecma]] standard compliant [[.NET Framework|.NET]] compatible set of tools. In 2011, [[Mono (software)|Mono]]'s support for System.Windows.Forms as of [[.NET Framework version history#.NET Framework 2.0|.NET 2.0]] was announced as complete;<ref>{{cite web

In 2011, [[Mono (software)|Mono]]'s support for System.Windows.Forms as of [[.NET Framework version history#.NET Framework 2.0|.NET 2.0]] was announced as complete;<ref>{{cite web

| url=http://www.mono-project.com/WinForms

| title= WinForms

| publisher=mono-project.com

| quote=''Support for Windows Forms 2.0 is complete. At this point, we are largely just fixing bugs and polishing our code. ''

| accessdateaccess-date=2011-07-30}}</ref>

System.Windows.Forms 2.0 works natively on Mac OS X.<ref>{{cite web

| url=http://www.mono-project.com/FAQ:_Winforms

Line 97 ⟶ 101:

| publisher=mono-project.com

| quote=''Does Winforms run on OSX? Yes, as of Mono 1.9, Winforms has a native OSX driver that it uses by default''

| accessdateaccess-date=2011-07-30}}</ref>

However, System.Windows.Forms has not been actively developed on Mono.<ref>{{cite web

|url=http://tirania.org/blog/archive/2011/Mar-07.html

Line 103 ⟶ 107:

| last=de Icaza

| first=Miguel

| authorlinkauthor-link=Miguel de Icaza

|date=2011-03-07

|accessdateaccess-date=2011-07-30

|quote=''For tools that are mostly OpenGL/DirectX based, use Windows.Forms, keeping in mind that some bug fixing or work around on their part might be needed as our Windows.Forms is not actively developed.''}}</ref>

Full compatibility with .NET was not possible, because Microsoft's System.Windows Forms is mainly a wrapper around the [[Windows API]], and some of the methods allow direct access to Win32 [[Callback (computer programming)|callbacks]], which are not available in platforms other than Windows.<ref name="monofaq-winform"/> Mono's WinForms implementation is based on Mono's libgdiplus, which implements [[GDI+]] on top of [[Gtk]] and [[Pango]].<ref>{{cite web |title=Mono / libgdiplus · GitLab |url=https://gitlab.winehq.org/mono/libgdiplus |website=GitLab |language=en}}</ref>

A more significant problem is that, since version 5.2,<ref>{{cite web

|url=https://www.mono-project.com/docs/about-mono/supported-platforms/macos/

| title=Introduction to Mono on macOS

| publisher=mono-project.com

| accessdateaccess-date=2019-11-12

}}</ref>

Mono has been upgraded so that its default is to assume a 64 bit platform.

Line 120 ⟶ 125:

| last=Martin

| first=Jess

| accessdateaccess-date=2019-11-12

}}</ref>

As of this date{{when|date=January 2021}}, a 64-bit version of System.Windows.Forms for use on Mac OS X remains unavailable and only .NET applications built for the 32 bit platform can be expected to execute.

== See also ==

Line 136 ⟶ 141:

== External links ==

{{Wikibooks|.NET Development Foundation}}

<!--===========================({{NoMoreLinks}})===============================

| PLEASE BE CAUTIOUS IN ADDING MORE LINKS TO THIS ARTICLE. WIKIPEDIA IS |

Line 157 ⟶ 163:

{{Widget toolkits}}

[[Category:.NET Frameworkterminology]]

[[Category:2002 software]]

[[Category:Formerly proprietary software]]

[[Category:Free and open-source software]]

[[Category:Microsoft application programming interfaces|Forms]]

[[Category:Microsoft free software]]

[[Category:Mono (software)]]

[[Category:Software using the MIT license]]

[[Category:Widget toolkits]]

[[Category:2002Windows-only free software]]