Visual Studio Solution Structure

Topics: Prism v2 - WPF 3.5
Jul 21, 2009 at 7:33 PM

We are using PRISM for all of our new applications.  We are developing a PRISM Shell Wpf Application to be used with a number of solution application domains.

What is the best way to structure the Visual Studio solution for each new application?

Do we Copy the shell application to each team project or solution subfolder?

Can we just refer to the common shell and somehow provide a new configuration file for the shell?

 

Jul 22, 2009 at 6:06 PM

Hi cscnut, 

This will greatly depend on your specific requirements and scenario, but beside the two approaches you suggested you might also consider creating VS templates with the "common shell" code. This will not only allow you to have a standard starting solution structure for all projects but in the future you might also enchase it will custom recipes for usual tasks. This is the approach which is used in p&p software factories (for example in the WCSF you have templates for creating new Web Sites and WAP solutions). 

This approach is similar to your first suggestion but automatized and integrated with VS but more difficult to achieve. So it will depend on how many new solutions based on this structure you will be creating to decide whether or not it worth the effort.
If you decide taking this approach you might find useful the following posts as starting point:

Compared with your second suggestion it's different regarding updates. Using your second approach updates/modifications to the "common shell" will automatically propagate to all projects. This might be both good or bad depending on your requirements. Using the VS templates approach (or the xcopy one) each project can make customization to the "common shell" without affecting other projects.

Hope it helps! 

Matias Bonaventura
http://blogs.southworks.net/matiasb

Jul 22, 2009 at 6:28 PM


Thank you for your suggestions. I will investigate these blogs and try and figure out if they will work for us.