Just like Abstract Window Toolkit (AWT), the agnate Java API, Windows Forms was an aboriginal and accessible way to accommodate graphical user interface apparatus to the .NET Framework. Windows Forms is congenital on the actual Windows API and some controls alone blanket basal Windows components[1]
Windows Forms provides a cross-platform way to architecture graphical user interfaces. However WinForms is mainly a adhesive about the Windows API, and some of the methods acquiesce absolute admission to Win2 callbacks, which are not accessible in added platforms than Windows[1].
Windows Forms has been in aftereffect abolished by Windows Presentation Foundation (and its associated GUI allegorical accent alleged XAML). Since WPF is almost new, it is cryptic if Windows Forms will abide to be bigger in approaching .NET releases
Windows Forms provides a cross-platform way to architecture graphical user interfaces. However WinForms is mainly a adhesive about the Windows API, and some of the methods acquiesce absolute admission to Win2 callbacks, which are not accessible in added platforms than Windows[1].
Windows Forms has been in aftereffect abolished by Windows Presentation Foundation (and its associated GUI allegorical accent alleged XAML). Since WPF is almost new, it is cryptic if Windows Forms will abide to be bigger in approaching .NET releases
No comments:
Post a Comment