We were building out the next version of an in-house thick-client application using WPF/Prism (Composite Application Library). As we were nearly done with the client our team was put under new management and shortly thereafter:

1. We were then directed to drop the Prism framework to keep things simple. This includes not using any type of Inversion of Control.

2. We were directed to build out the WPF application without using MVVM or similar; and more along the lines of a traditional WinForm application. The idea is that if a developer sees a control in Visual Studio’s designer view, then (s)he should be able to click on the control and see exactly what it's doing without having to traverse through a view-model (or similar).

3. We have now been tasked with building out the WPF application using one primary Window, use a Frame Control to contain the content, and use a Ribbon outside of the frame for the menu items. Reason we were provided to use Frame Control:

   a. We will show a view in the Frame with a Page (not a user control) and then load the page in the Frame.

   b. When a new view is to be shown in the Frame, the current view (Page) will be closed/disposed and the new view (Page) will take its place in the Frame.

   c. When a developer looks at the Page in design view, (s)he will be able to click on any control and see exactly what is being done.

Given the restrictions of 1 and 2 above, we’d like to present another method of building out the application that:

1. Can be presented as an alternative to using the “Frame Methodology” (item 3 above) but still provides the same type of functionality.

2. Does not use MVVM (see #1 and #2 above).

Provided the direction we’ve been given, any suggestions as to an alternative we can present? I’d request that the responses be kept on the professional level and thank you in advance.