Tagged Questions
1
vote
2answers
155 views
Why DependencyProperties and not native language support?
With advent of WPF and MVVM Microsoft introduced DependencyProperties and INotifyPropertyChange interface to provide a way to implement the "reactive" approach used with those technologies.
Sadly ...
1
vote
2answers
406 views
How to organize MVVM files in solution
I'm fairly new to the MVVM concept but like a lot of the flexibility it gives me so far. However, I'm struggling to find a good way to manage my code. I have several classes that are just sitting in ...
0
votes
0answers
159 views
Are both the EventAggregator used by ViewModel and Domain Event used by Model the same thing?
My initial doubt was should the Model classes in an MVVM use the EventAggregator or the traditional delegates in C# for events. I searched around and read about the Domain Events. It seems to me that ...
1
vote
1answer
166 views
Is there a clean separation of my layers with this attempt at Domain Driven Design in XAML and C#
I'm working on an application. I'm using a mixture of TDD and DDD. I'm working hard to separate the layers of my application and that is where my question comes in.
My solution is laid out as ...
2
votes
2answers
651 views
Hierarchical View/ViewModel/Presenters in MVPVM
I've been working with MVVM for a while, but I've recently started using MVPVM and I want to know how to create hierarchial View/ViewModel/Presenter app using this pattern.
In MVVM I would typically ...
1
vote
2answers
326 views
How do I know if I'm violating MVVM with WPF?
I was recently grabbing an auto generated TreeViewItem from a nested TreeView node in WPF, and I was using ItemContainerGenerator to get it in code behind. Then I thought to myself I'm certainly ...
5
votes
4answers
865 views
How to make creating viewmodels at runtime less painful
I apologize for the long question, it reads a bit as a rant, but I promise it's not! I've summarized my question(s) below
In the MVC world, things are straightforward. The Model has state, the View ...
4
votes
1answer
103 views
Contract / Project / Line-Item hierarchy design considerations
We currently have an application that allows users to create a Contract. A contract can have 1 or more Project. A project can have 0 or more sub-projects (which can have their own sub-projects, and so ...
5
votes
1answer
216 views
wizard-like data collection implementation help (next, next, finish)
I'm beginning to build an interface for our field techs to close out work orders and we have many different required paper forms for different customers. I had hoped to build a system where i can set ...
4
votes
1answer
507 views
Which notification pattern is preferable?
I'm working on a view model for a view that presents a dialog with export options. The user selects options then clicks Export. When the view model completes the Export, the calling view model ...
4
votes
3answers
922 views
How to use a MessageBox using the MVVM pattern?
I am implementing a UI application using the MVVM design-pattern.
The thing is, sometimes when you detect that something is wrong with data that was inputted by the user, you'd like to notify him ...
4
votes
2answers
590 views
MVVM Reporting App Approach ? Data Access Layer?
I'm trying to follow the MVVM pattern in a reporting / statistics application that I'm making in C# / WPF.
I have made many model classes to hold properties as a starting point. Some of these models ...
3
votes
2answers
802 views
What are the pros and cons of the MVVM architecture?
In class today we were introduced to the MVVM architecture for Silverlight/WinPhone/WPF; it looks nice for big projects, but what are your thoughts on MVVM?
What are the pros and cons?
I want to get ...
0
votes
2answers
310 views
What is the most pragmatic & basic UI pattern to follow for Silverlight and/or WPF
Here is the context. The apps will:
consume existing (and standard) web services.
app is UI intensive (UI updated frequently and lot of data to display).
development team experience level is ...
4
votes
1answer
733 views
Is ViewModel with more than one repository bad?
I'm working on a project with MVVM.
Some ViewModels have more than one repository.
Is ViewModels with more than one repository bad?
Please provide with why it's good/bad.
