The Model View ViewModel (MVVM) is an architectural pattern used in software engineering that originated from Microsoft as a specialization of the presentation model design pattern introduced by Martin Fowler.
1
vote
0answers
57 views
WPF, PRISM, MVVM and Outlook style desktop application: But isn't WPF dead? (Confused) [on hold]
We are currently planning in developing a, fairly big, desktop application. It’s an application composed of other applications similar to outlook. We will be a team of developers working independently ...
1
vote
2answers
167 views
I know the language but still can't code like other peers [closed]
I have moved to a new job and code base (been doing C#, .NET, Windows Forms, etc. for last four years) and I have been on this for three months until today. During these three months I caught up with ...
2
votes
1answer
60 views
Where does non-MVVM code belong in an MVVM app?
By non-MVVM code, I mean things like highly generalized components, like one with common extension methods for CLR types, and other 'homeless' helper classes etc? I have a Core project that most ...
1
vote
0answers
56 views
Should IoC container be part of portable library?
I am seeing the benefits of Portable Class Libraries for centralizing Models and ViewModels to a single code-base. Where should dependency injection management (IoC container) take place, though? My ...
4
votes
0answers
71 views
Loose Coupling Presenter to View in MVP
We work in a Java shop here and our web application uses an implementation of the MVP architectural pattern. Our manager comes from a .NET world, where he has been exposed to the MVVM design pattern. ...
1
vote
1answer
60 views
Help with complex MVVM (muli views)
I need help creating view models for the following scenario:
Deep, hierarchical data
Multiple views for the same set of data
Each view is a single, dynamically-changing view, based on the active ...
3
votes
1answer
99 views
When is it okay to reassign the model for a view in MVC?
Is it ever really acceptable to reassign the model for a view in MVC? (Or MV* where applicable.) In other words, for a single view instance, is it ever ok to reassign the view's model? That is, as ...
0
votes
1answer
122 views
What shoud MainWindow of a WPF contains
I am making a WPF application following MVVM model. I have seen some approaches for applying MVVM. I am concerned about my MainWindow.xaml. In some tutorials I have seen that MainWindow is only ...
1
vote
1answer
123 views
Syncing objects from code with the view in WPF
I've been reading some into it, but I am time pressed, so I would require a simple solution now and I promise to read up on it later. I come from a winforms c# background, and have lately been working ...
3
votes
2answers
197 views
Is a 'God' ViewModel desired in WPF
My application has user controls within user controls. Please see a screen shot of one of the most beautiful applications of all time (UC = user control):
All the properties live in the MainWindow ...
0
votes
0answers
91 views
wpf and mvvm printing report startegy
I am developing a WPF application and I need some clarity on printing in WPF and MVVM (I am using MVVM-Light).
I want to create standard looking reports for my application and I don't want to have to ...
1
vote
3answers
330 views
MVVM and service pattern
I'm building a WPF application using the MVVM pattern. Right now, my viewmodels calls the service layer to retrieve models (how is not relevant to the viewmodel) and convert them to viewmodels. I'm ...
2
votes
0answers
92 views
Sub routing in a SPA site
I have a SPA site that I'm working on, I have a requirement that you can have subroutes for a page view model. Im currently using this 'pattern' for the site
MyApp.FooViewModel = MyApp.define({
...
6
votes
3answers
2k views
What the best way to wire up Entity Framework database context (model) to ViewModel in MVVM WPF?
As in the question above: What the best way to wire up Entity Framework database model (context) to viewModel in MVVM (WPF)?
I am learning MVVM pattern in WPF, alot of examples shows how to implement ...
2
votes
0answers
92 views
When using MVVM, should you create new viewmodels, or swap out the models?
Say I have a viewmodel like this:
public class EmployeeViewModel
{
private EmployeeModel _model;
public Color BackgroundColor { get; set; }
public Name
{
get { return ...
