WPF Switching Views With Navigation Using MVVM And Dependency Injection
HTML-код
- Опубликовано: 14 янв 2023
- WPF Switching Views With Navigation Using MVVM And Dependency Injection this tutorial will show you how to switch views in wpf using MVVM and dependency injection using C# the programming language and WPF the programming UI framwork in order to navigate through multiple views you can use this with multiple windows as well this is a tutorial and a guide on how to create a professional wpf application using C# and how to navigate through multiple views in WPF.
Patreon: / payloads
Discord: / discord 
Наука
Patreon: www.patreon.com/payloads
Discord: discord.gg/kNFPKhvnYz
this video just saved my life. I had some code with very half-baked ideas on how to do exactly this but it just wouldn't work, and spent like 1.5h following along with the steps you take to reform what i had and see the advantages of your approach. And really, it works absolutely beautifully, so thank you even a year later :)
Went through this video about 2 weeks ago and was just stumped as to why things were done in certain ways. After leaning more about the need for ObservableObject and RelayCommand I came back to this video today and just breezed through it. Really good video. Thank you
Beautiful, you cant imagine how long I have been looking for this, it is exactly what I needed. Thanks!
I'm glad you found it useful! :-)
Absolutely amazing. Right what I was looking for. After searching for this on You tube and Linked, landed on this video after many months. Thanks for your help.
I'm glad you foudn something that was useful! :-)
Deffinitly best tutorial videos on wpf on YT. Thanks mate Also those videos on how to make Flat Design they are perfect
Thank you for this tutorial, I must say it is the simplest I ever watch. For the next can you make a tutorial about passing data using this navigation. Thank you!
Thanks alot. Fast and comprehensive information I needed. It's rare to find so much information in such a short video.
I'm glad you found it useful! Thanks for the nice feedback!
Thank you for this great tutorial! As a newbie this was really informative.
Heck yeah! I'm glad you found it useful! :-)
so nice to see you back!
Glad to be back :D
I was so happy to finally see a video again. greate job
Thank you! Happy to see that you're still around! :-)
@@_buffer 💚💚💚
Amazing as always ❤️
This was amazing. Thank you so much. 👍
You're most welcome! :-)
Thank you for this video, very helpfull, i was wondering how to pass parameters with navigation, i changed the factory from Func to Func so i can pass parameter as an object, but i don't know if this is the right way, even if it works
Fantastic tutorial!! 😊
Thank you so much! :-)
Thank you. Wouldn't it be a bit more modulable if instead of derivating the Core, having a IServiceNavigation interface ? Then simply init the class with the navigation, then its command... Nit picking I guess, but it woudl feel more reusable.
This is what i needed, and you explained well, however did not figured out what is (???) at 17:26 , I had to remove it for me to work.
For some reason "ContentControl" in MainWindow is displaying the name of the viewmodel class file name rather than display the view that it's associated to?
Very useful what you did here!
Thank you! I'm glad you found it useful! :-)
Great video, you got a new subscriber (:
Awesome, would love to see a version using community toolkit and what that would change.
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.
Really nice video, i have learned a lot from you and this video! One thing though im a bit confused of is how do to set the other ViewModels DataContext? Its just i have tried something, that doesnt work the way i expected... You can try it youself by deleting the MainViewModels ButtonBindings, and then try to press the buttons on either HomeView or SettingsView. When i try it, it doesnt work?
nice video, it helps me alot!
Thank you for this wonderful video. I would like to know if you have this same video without core anymore by using microsoft mvvm please? thank you so much.
Do you still need OnPropertyChanged in the setter of the Navigation property in the MainViewModel Class. There is already an OnPrpertyChanged in the setter of the CurrentView of the NavigationService
Thank you for this great video. Please at 16:14, I cant see well the parameters of RelayCommand execut:0:oject=>{...} doesnt work for me, i had to rewrite as a function. do you mind ,please, to post only that part here? thank you again for this great job very helpful
Same error
Well I got through this toward the end but new RelayCommand(execute: o:object => gives errors.
are UserControls created every time we click a button to go to them, or they have only one instance?
What if you open windows? Do i register the view models as transient? It is complicated when you have to use child forms
great job🤪
Which theme do you use in Rider?
Does this code create new instance of someViewModel every time you change views? how to create and use only 1 instance for every viewmodel?
Oh man, a service locator, can we do it without the service locator?
hey! i know its been like 7 months since you posted this but is there any way you could tell me how id set a default CurrentView? i want the homeview i have to be a navigation hub and i cannot for the life of me figure it out. thanks!
edit: also, how do i pass in a variable to a view im switching to?
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();
}
Great tutorial. Totally cool, simple but effective. where can we get the source code, save me some key strokes. Thanks,
Thank you! And the source code can be found over at my Patreon www.patreon.com/payloads
Hello, nice tutorial. just wondering if there is a simple way to pass parameters to other viewmodels when navigating to one?
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.
How to set child view model properties from parent? When i do that, the child User Control displayed on the main window parent does not change its properties, i have set the data context
Hello Payload! I have a question. Maybe it`s kinda stupid question. So, should i use MVVM when i have a lot of different windows with different functionality (I am making diary, and there I have MENU window and other window where I working with all that writing stuff)?
So, I have 3 groups
(1.Main menu window and window with all writing and editing stuff,
2. account settings and customizing window to change look of main menu window (i have button on main menu window to navigate to them)
3. Login and registration).
I guess they would look good with MVVM, but i am not sure if they can be putted together like that. Should i put all those windows that i work with, right into folder MVVM, and working there with those groups? Thank you in advance
Good question! If you join the Discord it'll be easier to help you :-)
Thank you very much for this great video. I studied a lot by myself, finally I can do it.
BTW, may I ask that, is it possible to do a multi-navigation.
For example, 2 views in 1 window, and there are 2 subviews in one view of window.
It can be contentcontorol or tabcontrol.
Thanks.
Look at view model locator concept
I have similar code but I dont need creating new instance of viewmodel every time I change views. I have a lot of data that viewmodels are storing and this method of changing views would terribly slow down the program
can u do a updated version of the chat hub with a login and setup the database but make it where it saves the last chats and how to add calling and video chat and make it a add function plz
Great video. I had to use a magnifying glass to view the code. Font is too small.
nice
Thank you Yousef! :-)
Great tutorial. But the volume is a little on the low side.
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 :-)
@Payload what is the name of IDE you used?
Rider :-)
What does (???). in the various Path's mean?
I have the same issue. I have never seen this before.
What keyboard do you use?
Custom keyboard with nk_sherbet switches :-)
ty bro
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 :-)
Hello, can someone tell me how to make authorization with this code? Those. so that I can log into my account and I can get the UserControl output working.
I'm stuck at 16:12. where you do NavigatoToHomeCommand = new RelayCommand(execute: O :object.... I get a bunch of errors, starting with the fact that O is unknown...
new Relaycommand(o => ...) get rid of execute::Object
Wait so you don't use pages for navigation?
Hi i applied this method for my new project and it ran fine for a while, however now i am getting sudden Errors in my app.xaml telling me that my sources that i use for my viewmodels and views do NOT exist within the previously used and until then working namespaces. I tried reloading the folders into the project but to no success. Its beginning to get really frustrating as i am no longer able to compile my project. Does anybody know how to handle this?
I saw another example where an AppHost is used to manage the DI container: ruclips.net/video/dLR_D2IJE1M/видео.html . I wonder what the benefit the AppHost brings versus the ServiceCollection approach used in this video.
is it working under .NET 6?
Yep, it works across all .NET Versions > 4.5
what ide Is that
whys bro awake at this time
Because content! :D
It's so complicated :/ I don't understand why this is such a different approach from what you used to switch views before. In your previous video ('Modern UI app') you made it much simpler, just reassigning CurrentView with Command on click, and switching between views worked the same.
Couldn't it be done as easily as in that video? I appreciate that you show how something is done, but if this is supposed to be a tutorial, it would be better if you did a longer introduction before doing it, what and why exactly you want to do.
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
What a complicated mess only to do that. I should be a more simpler way
😂 i can't believe this either. looks like an April fool's joke. this ain't "easy"
I hate youtubers like this. who don't even share the code if we don't pay.
Layne was better
beautiful #FFE51400