Overview: WPF
-
Why WPF To build Desktop applications, Microsoft came up with numerous APIs over the years, like Win32 API, MFC, VB 6.0 and lately .NET Winform. Typically in a full fledged desktop application, you would like to have diverse User interfaces like controls, 2D Graphics, 3D-Graphics and may be optionally (say by clicking on Advanced.. button) you want to have Media and Animation. Looking at above APIs from Microsoft, It is difficult for a Windows Programmer to master diverse nature of each API for a particular User interface. Apart from this, in all above technologies more or less the overall Layout was fixed. In other words, Layout couldn't adapt itself easily to different window sizes. Finally, In all above technologies, there is no way to separate the Graphical contents from code. Say e.g in WinForm Apps, when you drag and drop a control on a form surface framework generates C# code. It also means that to change the look and feel of any control you will have to deal with code. This is where Microsoft came up with 'Windows Presentation Foundation' (WPF) Windows Presentation Foundation is a one of the .NET components which allows you to develop the Next Generation Desktop Application with very rich user interfaces. WPF is available from .NET 3.0 onwards. It is one of the components of .NET 3.0 and .NET 3.5 frameworks ------------------------------------------------------------------------------------------------- WPF Features: 1) Single Unified programming Model for different User Interfaces like 2D Graphics, 3D Graphics, Media, Document API and Animation 2) Declarative User interface through XAML 3) Separation of Business logic from UI part through *XAML 4) Flexible Layout Model (no use of coordinates of control w.r.t to window) 5) Lookless controls (without fixed size) 6) Enhanced Designer and Developer productivity. Designer can work on UI aspect through *XAML file and developer would be busy with corresponding .cs file 7) Powerful data binding model 8) Hardware acceleration. WPF drawing is performed through DirectX. --------------------------------------------------------------------------------------------------- WPF's basic programming Infrastructure -> Declarative programming Style using *XAML (Using XAML is optional) -> Dependency Properties wrapped under normal .NET properties -> Routed Events -> Control Commands --------------------------------------------------------------------------------------------------- *XAML (Zammel) is XML based mar
-
Why WPF To build Desktop applications, Microsoft came up with numerous APIs over the years, like Win32 API, MFC, VB 6.0 and lately .NET Winform. Typically in a full fledged desktop application, you would like to have diverse User interfaces like controls, 2D Graphics, 3D-Graphics and may be optionally (say by clicking on Advanced.. button) you want to have Media and Animation. Looking at above APIs from Microsoft, It is difficult for a Windows Programmer to master diverse nature of each API for a particular User interface. Apart from this, in all above technologies more or less the overall Layout was fixed. In other words, Layout couldn't adapt itself easily to different window sizes. Finally, In all above technologies, there is no way to separate the Graphical contents from code. Say e.g in WinForm Apps, when you drag and drop a control on a form surface framework generates C# code. It also means that to change the look and feel of any control you will have to deal with code. This is where Microsoft came up with 'Windows Presentation Foundation' (WPF) Windows Presentation Foundation is a one of the .NET components which allows you to develop the Next Generation Desktop Application with very rich user interfaces. WPF is available from .NET 3.0 onwards. It is one of the components of .NET 3.0 and .NET 3.5 frameworks ------------------------------------------------------------------------------------------------- WPF Features: 1) Single Unified programming Model for different User Interfaces like 2D Graphics, 3D Graphics, Media, Document API and Animation 2) Declarative User interface through XAML 3) Separation of Business logic from UI part through *XAML 4) Flexible Layout Model (no use of coordinates of control w.r.t to window) 5) Lookless controls (without fixed size) 6) Enhanced Designer and Developer productivity. Designer can work on UI aspect through *XAML file and developer would be busy with corresponding .cs file 7) Powerful data binding model 8) Hardware acceleration. WPF drawing is performed through DirectX. --------------------------------------------------------------------------------------------------- WPF's basic programming Infrastructure -> Declarative programming Style using *XAML (Using XAML is optional) -> Dependency Properties wrapped under normal .NET properties -> Routed Events -> Control Commands --------------------------------------------------------------------------------------------------- *XAML (Zammel) is XML based mar
Errm. Thank you? I already know this though - perhaps you might want to put it on a blog somewhere, rather than in a forum.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Why WPF To build Desktop applications, Microsoft came up with numerous APIs over the years, like Win32 API, MFC, VB 6.0 and lately .NET Winform. Typically in a full fledged desktop application, you would like to have diverse User interfaces like controls, 2D Graphics, 3D-Graphics and may be optionally (say by clicking on Advanced.. button) you want to have Media and Animation. Looking at above APIs from Microsoft, It is difficult for a Windows Programmer to master diverse nature of each API for a particular User interface. Apart from this, in all above technologies more or less the overall Layout was fixed. In other words, Layout couldn't adapt itself easily to different window sizes. Finally, In all above technologies, there is no way to separate the Graphical contents from code. Say e.g in WinForm Apps, when you drag and drop a control on a form surface framework generates C# code. It also means that to change the look and feel of any control you will have to deal with code. This is where Microsoft came up with 'Windows Presentation Foundation' (WPF) Windows Presentation Foundation is a one of the .NET components which allows you to develop the Next Generation Desktop Application with very rich user interfaces. WPF is available from .NET 3.0 onwards. It is one of the components of .NET 3.0 and .NET 3.5 frameworks ------------------------------------------------------------------------------------------------- WPF Features: 1) Single Unified programming Model for different User Interfaces like 2D Graphics, 3D Graphics, Media, Document API and Animation 2) Declarative User interface through XAML 3) Separation of Business logic from UI part through *XAML 4) Flexible Layout Model (no use of coordinates of control w.r.t to window) 5) Lookless controls (without fixed size) 6) Enhanced Designer and Developer productivity. Designer can work on UI aspect through *XAML file and developer would be busy with corresponding .cs file 7) Powerful data binding model 8) Hardware acceleration. WPF drawing is performed through DirectX. --------------------------------------------------------------------------------------------------- WPF's basic programming Infrastructure -> Declarative programming Style using *XAML (Using XAML is optional) -> Dependency Properties wrapped under normal .NET properties -> Routed Events -> Control Commands --------------------------------------------------------------------------------------------------- *XAML (Zammel) is XML based mar
amazing list of features that were never pain points