Good reasons NOT to place ViewModels in separate assembly?

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.

<

Answer 1

The actual question is ... what are assembles for?

They are a way to separate logic making it unavailable to other code unless you add a reference, so in fact they are a way of hiding parts of code from other parts.

Given this purpose and the way you are using it I would say that you're doing it right.

Having said that I find much easier to verify that the Views do not have any code behind in code reviews and keep the views in the same assembly. Less projects = faster compile and load times.