Value of MVVM in a Line of Business Application (and a Rant of Current Development Practices)
After 2 years, I’m still struggling with MVVM as a practical method of producing working software. In some cases it’s great. I did a multithreaded application that controlled a small assembly line that would have been a nightmere without MVVM concepts. An abstraction from the physical assembly line was almost a no brainer.
Value of MVVM in a Line of Business Application (and a Rant of Current Development Practices)
After 2 years, I’m still struggling with MVVM as a practical method of producing working software. In some cases it’s great. I did a multithreaded application that controlled a small assembly line that would have been a nightmere without MVVM concepts. An abstraction from the physical assembly line was almost a no brainer.
Dependency properties outside the realm of WPF?
Is there a more general concept or name for what WPF calls “dependency properties”? I imagine this is not a WPF-ism and in fact other libraries or frameworks have employed a similar approach? If so, what are these other instances and what are the similarities and differences compared to Microsoft’s dependency properties?
Dependency properties outside the realm of WPF?
Is there a more general concept or name for what WPF calls “dependency properties”? I imagine this is not a WPF-ism and in fact other libraries or frameworks have employed a similar approach? If so, what are these other instances and what are the similarities and differences compared to Microsoft’s dependency properties?
Dependency properties outside the realm of WPF?
Is there a more general concept or name for what WPF calls “dependency properties”? I imagine this is not a WPF-ism and in fact other libraries or frameworks have employed a similar approach? If so, what are these other instances and what are the similarities and differences compared to Microsoft’s dependency properties?
Dependency properties outside the realm of WPF?
Is there a more general concept or name for what WPF calls “dependency properties”? I imagine this is not a WPF-ism and in fact other libraries or frameworks have employed a similar approach? If so, what are these other instances and what are the similarities and differences compared to Microsoft’s dependency properties?
Dependency properties outside the realm of WPF?
Is there a more general concept or name for what WPF calls “dependency properties”? I imagine this is not a WPF-ism and in fact other libraries or frameworks have employed a similar approach? If so, what are these other instances and what are the similarities and differences compared to Microsoft’s dependency properties?
Why, in WPF, do we set an object to Stretch via its Alignment properties instead of Width/Height?
In WPF’s XAML, we can tell an element to fill its container like this:
Why, in WPF, do we set an object to Stretch via its Alignment properties instead of Width/Height?
In WPF’s XAML, we can tell an element to fill its container like this:
Why, in WPF, do we set an object to Stretch via its Alignment properties instead of Width/Height?
In WPF’s XAML, we can tell an element to fill its container like this: