.net – Smart client software factory view activation

We used SCSF for a real world app with about 10 developers. It was a steep learning curve to set up and develop a pattern of usage, but once it was set up, introducing new developers to the project was VERY easy. Using CAB and SCSF was very beneficial to our project especially getting each developer up to speed and productive.

A downfall of SCSF is that it provides ALOT of functionality that may not be used (we probably only used 60% of the functionality).

I am also using SCSF for a new project and am considering refactoring to PRISM. PRISM allows you to cull the functionality that is not used. If you use WPF, I suggest looking into PRISM.

In general, no, that's not how the pattern(s) work. The Model is the reusable portion, and the combination of V + C/P comprise the application layer, and therefore are application-specific by definition.

If you have logic in your presenters that seems like it should be reusable across different applications, you should look at how you can push that down into your domain layer, and make it part of your Model.

This is one of the best articles on the subject.