WPF Switching Views With Navigation Using MVVM And Dependency Injection 

I beg you for explanation video for idiots (like me) what is what, for example what we are exactly doing in App.xaml, what is IServiceCollection etc. ok, so I watched to the end, and I'm completely lost ): . I mean I understand base functionality but func? NavigationService? idk. And yes i know documentation i looked at it and 0-0. I will Love explenation viedo on this exact project.

@cebulaczerwona3425 This is the one missing from all over internet! No one explains what he does and why he does it!! They just keep typing and typing and typing... What's the point of spending hours typing a code that could be presented as a source code!! Either they do that to earn money or they do NOT know how to teach!! If you want to teach something to someone you need to go down to the level of the learner and realize the questions that he would be asking if you were face to face with him!! Unfortunately there are no good teachers. They just typing and typing... I have subscribed here but I am disappointed... And what is the point of narrating something like you are in a hurry to go to the loo!! To teach someone you need to be not only a good programmer but also a good teacher!! Once again disappointed!!

I understand where you're coming from, and the issue is that explaining that would require it's own video. A good idea would look at the implementation in the video and try to understand what's going on combined with MSDN for instance. Or join the Discord server and ask more direct questions there. Appreciate the feedback! @@niangel2704

Agree with this, especially growing popularity of community toolkit, video would be useful

I second this! Does the new toolkit provide means for navigation using services and DI?

If you want to use the Community Toolkit, you can simply use derive from Observable Object instead of creating a ViewModel class, and use the RelayCommand provided by the Community Toolkit, at least that is what I've done and works like silk.

Same error

Thank you so much! :-)

Good question! If you join the Discord it'll be easier to help you :-)

Because content! :D

😂 i can't believe this either. looks like an April fool's joke. this ain't "easy"

I'm glad you found it useful! :-)

I have the same issue. I have never seen this before.

I'm glad you foudn something that was useful! :-)

Rider :-)

Error was indeed in xml file. You need to make sure its `UserControl` class and not any other

welp, I got the pop out thing myself lol

Yep, it works across all .NET Versions > 4.5

Thank you! And you're most welcome :-)

in your OnStartup method in App on the video, put var navService = _serviceProvider.GetService(); navService.NavigateTo(); and to the second question, i think you need to get rid of the in-line delegate when defining NavigateHomeCommand for example and instead pass in an actual function which can change the properties of a class which other viewmodels can access. hope i could help a little bit

You can do this by calling the NavigateTo function in the MainViewModel like this public MainViewModel(INavigationService navService) { Navigation = navService; NavigateToHomeCommand = new RelayCommand(o => { Navigation.NavigateTo(); }, o => true); NavigateToSettingCommand = new RelayCommand(o => { Navigation.NavigateTo(); }, o => true); Navigation.NavigateTo(); }

This can absolutely be done in the simpler way that you mentioned. The difference in approach (and level of complexity) is a result of using the MVVM design pattern and Dependency Injection. Using MVVM and DI simply adds some benefits (e.g. easier unit testing, reduced overall complexity once you hit a certain app size) that some may feel are worth the added complexity, and it's those people that this video is targeting.

@@repossession ok

Good question! It's called Rider and it's developed by JetBrains!

lazy ahhh

Thank you! And the source code can be found over at my Patreon www.patreon.com/payloads

I'm glad you found it useful! Thanks for the nice feedback!

You sure it’s not on your side bud, volume is fine for me!

Thank you! The volume seems fine on my end too actually :-)

And how to allow Dependency Injection for Views eg. if someone what's to inject EventService into View.cs how would you do that?

did you get how to pass parameter to viewmodel? I want to open details of client (to edit), but I don't know how to do that

wow, I can't believe it, I asked chatGPT how to do it and he answered with working code :)

​@@AndrzejKlonowski Similar to how you set the DataContext when instantiating the MainWindow to the MainWindowViewModel you could initialize any property in your ViewModel when adding it to the serviceCollection. Additionally, since this should be an instance of your ViewModel, the work done in your constructor should be processed as well.

You need to change in your App.xaml StartupUri="MainWindow.xaml"> to StartupUri="MVVM/view/MainWindow.xaml">

new Relaycommand(o => ...) get rid of execute::Object

Heck yeah! I'm glad you found it useful! :-)

Thank you! Happy to see that you're still around! :-)

@@_buffer 💚💚💚

Custom keyboard with nk_sherbet switches :-)

You're most welcome! :-)

Thank you! I'm glad you found it useful! :-)

Thank you Yousef! :-)

Anytime! :-)

I had a problem yesterday about navigation. So, maybe u can help me. I have 4 different UserControls (views) on 1 page with one GlobalVoewModel. I had to switch (navigate) on one of UCs without changing the others. It's was very difficult and I came to solution by just using flipper element from MeterialDesign, but I actually don't like it. Any advices, payload?

@@_buffer bro

@@haku5957 Sounds like a design issue, feel free to hop in the Discord, will be easier to help you over there :-)

Look at view model locator concept