Building a Standard WPF Application
Loading...
Loading...
3:27
WPF Tutorial 1 - Basics of a WPF Applicationby wpftutorials13,944 views- 0:15
wpf conceptby flashfith41,552 views
- 7:37
Final Projectby idoprz19,499 views
- 5:24
WPF School Management System Demoby almaslar8,879 views
- 1:05
WPF application - Cool Moviesby lmolfino50,117 views
- 1:00
How to Use Easy Expression Halter Hands-Free Pumping Braby momandbabyshop1,656,924 views
- 2:57
WPF Simple Bindingby phpMyst2,398 views
- 0:39
MainFormby robinlolo39,241 views
- 5:03
WPF Database C# + Blend 3by xxandrejxx16,196 views
- 9:29
How to create a Glass Button in WPFby angelorohit21,919 views
- 0:48
WPF Login Form With Video Clipby hectorsmith7867,783 views
- 0:31
WPF Effectsby TheRHogue18,473 views
- 29:03
WPF Tutorial 1: How to Create a Custom Window Border.by windowsUNLOCKED6,818 views
- 1:41
LoginGlazz ; login prompt visual basic wpfby flashfith15,946 views
- 4:31
WPF Finance Applicationby jobikjoy29,072 views
- 3:41
MVVM in WPF and Silverlight - Part 1by rainerstropek18,654 views
- 4:46
Intro to WPF Part 3: Richer Typographyby fortesdotcom12,037 views
- 0:10
WPFby dotnetcool29,696 views
- 8:10
PowerBuilder .NET: The Basics - A WPF Database Application in Less Than 7 Minutesby SybasePowerBuilder10,635 views
@mscott3564 totally agree, seperation of interface and business logic is critical, and without data binding, the power of wpf is completely missed
mscott3564 2 months ago
this is not really a good idea for use in wpf. in wpf, the interface should be seperate from the code logic. use of data binding and seperation of concerns is a critical key to making good use of wpf. With the design pattern used here, you might as well use win forms
mscott3564 4 months ago 2
1 person if completly dumb. Why? Because the creator of this video didn't use a shitty music in his video so he could thumbs down. The creator made a pretty good tutorial. That 1 person doesn't know how to apreciate things.
MaximMike9800 5 months ago 2
@donzaliko "x:Name" is part of the XAML language standard. "Name" is the property of the element you create. But, because ALL WPF elements have the "Name" property, it doesn't matter which one you use. If you create your own class you must use the [RuntimeNameProperty = "Name] attribute on your class in order for this to still be true. If you DO NOT include this attribute then you MUST use x:Name.
YesYou123333 1 year ago
guys what different is between
x:Name="asdasd" and Name="asdasd"
please reply
donzaliko 1 year ago
Question: In your OnClosing() method for Window1, why do you call base.OnClosing() first? Shouldn't you ask the question BEFORE you call the base.OnClosing() ? Otherwise I would say you're playing with fire.
whcernan 1 year ago
brilliant introduction to WPF and excellent way of describing. Thank you very much for this intro and am looking this from long time
kamalLitt81 1 year ago
AWESOME introduction! I have been trying to understand the way that the windows interact with each other and this tutorial has done what those who I have asked have not been able to
maloshzp 1 year ago
Excellent video that shows some how to do some common items. I especially needed to know how to take information typed into a second window and get it back into the owner window. Great and to the point.
bcook1000 1 year ago
Thank you very much for this tutorial. Basic, easy, and the screen was crystal clear.
getreadytotube 1 year ago