Recommendations for developing a WPF application without using MVVM or similar

Question

We built the next version of the internal application with a thick client using WPF / Prism (Composite Application Library) . Since we were almost done with the client, our team was transferred to a new management and shortly thereafter:

• Then we were asked to abandon the Prism framework so that everything was simple. This includes not using any type of inversion control.

• We were asked to create a WPF application without using MVVM or similar; and more through the traditional WinForm application. The idea is that if a developer sees a control in a Visual Studios designer’s view, then he should be able to click on the control and see what he does without moving through the view model (or similar).

• Now we are tasked with creating a WPF application using one main window, using Frame Control to contain the content, and for the menu items use a frame outside the frame. The reason we were given the use of Frame Control:

  and. We will show the view in a frame with a Page (rather than a user control), and then load the page in a frame.

  b. When a new view is shown in the frame, the current view (page) will be closed / deleted, and the new view (page) will take its place in the frame.

  with. When a developer looks at a page in view mode, he will be able to click on any control and see what exactly is being done.

Given the limitations of 1 and 2 above, wed would like to introduce another method for building an application that:

• It may be presented as an alternative to using the “Personnel Methodology” (paragraph 3 above), but still provides the same type of functionality.

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

If a direction were indicated, any suggestions for an alternative that we can provide? An identifier requires that answers be kept professionally and thanked in advance.

Answer 1

. ( , ...)

, , : " WPF, - , WPF ". , , , , , MVVM.

, :

, Visual Studios, ,

, MVVM , . , , ( ) .

. Windows Forms , , . , , , .

, , , MVVM. MVVM ViewModel, .

---

BTW. "" UserControl . , UserControls... Frame - , ( ). , , , - .

Answer 2

MVVM, ; .

, , , , , " , ".

, , - MVVM, , , .

, , , Emesary, #.NET Emesary .

:

    private void addButton_Click(object sender, RoutedEventArgs e)
    {
        GlobalTransmitter.NotifyAll(new Notification(NotificationType.CreateRecipe));
    }

. , , .

, , ( ) Frame. , . Emesary.

Answer 3

WPF-, . . : UserControls.

( ) . , , ?

, , "", ... "!" , .

№2 (MS bigs !). , , ( , ). , , ViewModels .

( ) VS, , , ViewModel ( Expression Blend ).

, MVVM (.. ViewModel , RelayCommands Mediator) , , , . , (, Josh Smith RelayCommand Marlon Grech Mediator - , ), MVVM .

WPF MVVM . WinForms, WPF. 2 .

Answer 4

, . , . , , MVVM, , / , , , .

, , " , ", : - , , . , SOC, OOP/OOD.

LOL. , derrive-, ... MVC/MVP .. MVVM , WPF.

: , MVVM, .