How to develop modules correctly?

Jan 10, 2012 at 3:19 PM


I've got a WPF application it's growing faster, so I decided to split in modules for having an easier manteinance... I've got some class I use as framework that extends Screen, some behaviors and so on... what's best for them? for now I've exported some view/viewmodels in a myProject.Modules.ModuleA.Client and I've created a myProject.Module.System where I put those classes (screen, helper,etc), now if I reference them as project reference, I'm again at the point that if I change somethin in the system dll I've to redevelop all the new assembly.... any suggestion?