Windows Forms (English Wikipedia)

Analysis of information sources in references of the Wikipedia article "Windows Forms" in English language version.

refsWebsite
Global rank English rank
6,158th place
4,128th place
low place
low place
153rd place
151st place
383rd place
320th place
low place
low place
low place
7,385th place
6th place
6th place
low place
low place
low place
low place

archive.org

github.com

  • "v8.0.0". github.com. 2023-11-14. Retrieved 2023-11-21.

hanselman.com

infoq.com

informit.com

  • De Smet, Bart (January 4, 2011). "Chapter 5". C# 4.0 Unleashed. Sams Publishing.

joshsmithonwpf.wordpress.com

  • Smith, Josh (2007-09-05). "WPF vs. Windows Forms". Josh Smith on WPF. Retrieved 2011-08-25. WPF is not intended to replace Windows Forms. [...] Windows Forms is still alive and well, and will continue to be enhanced and supported by Microsoft for years to come. WPF is simply another tool for Windows desktop application developers to use, when appropriate.

microsoft.com

msdn.microsoft.com

mono-project.com

  • "FAQ: Winforms". mono-project.com. 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
  • "WinForms". mono-project.com. Retrieved 2011-07-30. Support for Windows Forms 2.0 is complete. At this point, we are largely just fixing bugs and polishing our code.
  • "WinForms". mono-project.com. Retrieved 2011-07-30. Does Winforms run on OSX? Yes, as of Mono 1.9, Winforms has a native OSX driver that it uses by default
  • "Introduction to Mono on macOS". mono-project.com. Retrieved 2019-11-12.

tirania.org

  • de Icaza, Miguel (2011-03-07). "GDC 2011". Retrieved 2011-07-30. 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.