Question

I’m developing a project using the MVVM pattern in WPF.

One of the key benefits to MVVM is maintaining clear separation between business logic and presentation.

As a test to see how well separated everything actually was, over the weekend I spiked moving all ViewModels, Models, and business logic to a separate .dll. The .exe was left as a thin presentation layer.

This worked, seamlessly, first try.

I’ve already seen benefits to keeping views (xaml, presentation) in the .exe and core logic in its own dll. For example, there’s no longer any dilemma in my mind about whether code-behind in Xaml is an issue: I’m comfortable with it if it becomes necessary, since I know it’s presentation specific.

So far this exe/dll separation has worked so well that my question is: Has anyone experienced any downside to this approach?

Related question: Implementing MVVM in WPF without using System.Windows.Input.ICommand

Answer 1

2 weeks now with my Model & View Models in a dll, my xaml in an exe and no problems whatsoever.