For a front-end application broken down in a MV* manner, should I have models dedicated to UI logic?
I am not talking about simple UI logic like clicking a button directs you to another page, but where one action may result in several different of behavior depending on current application state, and may also trigger response in other parts of the application. Currently my view publishes all UI event so the response can be delegated to other parts. The problem is which other part? In order to avoid writing ‘fat’ controllers that hold arbitrary amount of domain logic, I thought it might be nice to have a non-persistent object that models UI behavior, but am not sure if this makes sense or if I am just pushing the problem around and being object-happy?
WCF service as a proxy for publishing real-time data to a WPF/MVVM clients
I’ve been tasked with creating a dashboard application to show real time updates for our servers. The raw data comes in from an XML file on our intranet which I need to parse and present to the user.
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 a folder in my solution such as xxxView.cs, xxxViewModel.cs, yyyView.cs, yyyViewModel.cs, zzzView.cs, zzzViewModel.cs you get the idea. It has started to crowd my solution, making it harder to find the files I’m looking for. Is there some standard way to organize these files? Do I create a View and ViewModel folder to separate and clean up the solution or have people found a better way?
Should code-behind in WPF be considered part of the view?
I’ve read plenty of articles around different patterns in use with WPF and this is something I’ve yet to understand: should a code-behind file be considered part of the view? As a consequence, should code-behind files be allowed utilise knowledge of specific elements in the markup?
What is this variation of MVC in JavaScript?
I am working on sorting out my Javascript code. Currently I have views implemented without any Model or collection. Now I working on separating Model from View. So for this transformation, I am planning as follows:
Should MVVM ViewModel inject an HTML template for default view?
I’m working on web application design that includes Knockout.js and have an overall MVVM question: Does it make sense for the ViewModel to automatically inject a default HTML template (pulled from separate file)?
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.
Checklist for coding MVVM web application [duplicate]
This question already has answers here: What does a standard code review contain? (5 answers) Closed 11 years ago. We are a small team working on a web application using MVVM design pattern using technologies like .NET, Knockout and HTML. I am trying to come up with a code review checklist for this, so that […]
Is MVVM in WPF outdated? [closed]
Closed 10 years ago.
Is MVVM in WPF outdated? [closed]
Closed 10 years ago.