I am so excited about this, I've heard about unit testing and never knew where to start, and now I've done it and can start contemplating how to integrate it into my other work. Thank you!
Great video. I think that they are just the right length. Some video tutorials are so long that they are exhausting to watch in one sitting and once I leave its tough to come back and try to find where you were and all that. But your videos can be consumed in one sitting and I can save the next video for the following day without breaking up the lesson. Just thought I'd be specific about what I like about them. Maybe it would help. Keep going.
Thanks for the feedback MSon! This has always been something I've wondered about. Personally, I prefer watching videos under 20 minutes, so I can definitely understand the fatigue with watching long videos. I sense that other people have similar preferences, so I rarely make 20+ minute videos anymore.
Hey Комиль, this would be a great application to implement roles for! Thank you for the suggestion. I will add this to the list of things to add down the road.
Hi, Why you have separate AuthenticationService and Authenticator? I see that Authenticator has extra functionality (CurrentAccount), this is all the reason? The second question is why the Authenticator is in the WPF project instead of the domain project?
Hey Sean, I love this series and have been following it to make some bug tracking software for my development portfolio. I'm a bit confused about why you made a new IAuthenticator interface that has its own Login and Register methods that just use the Login and Register methods from the IAuthenticationService interface that already exists? I know there is probably a reason, but why not just use the IAuthenticationService?
Hi, Thanks for wonderful content, I wonder if you could also implement Roles for users, like a user, superuser, Admin. block access to views depending on roles. thank you.
Hey Engineer-Development, if an async void throws an exception, it will crash the application. Additionally, any function that calls the async void will not be able to catch the exception. Preventing async voids from throwing any exceptions is the safest solution. Good question!
@@SingletonSean oh ok, so if it was an async method but that returns a datatype, that would be easier to debug and prevents app crashing or it's because of the fact that it is async?
Hello I am trying to understand and build Application and implement "new feautres" according to my possibilities. How can I implement that the currently logged in user is displayed (e.g. in the upper left corner) of the Home, Buy or Sell view / Main window? What would I have to do to add a logout or change user button.
A textblock with a binding to the currentUser's username. Logout button would probably just be a button hooked up to a command that calls Logout, and switching users is really just logging out then going to the log in view.
Hey - really like the content. Wondering if there was a more MVVM friendly approach for the password section? Was trying to avoid doing code behind if possible
Hey James, I'm the same way as you with avoiding code behind haha. It's not always terrible, but for this I would definitely prefer a bindable password box rather than relying on command parameters. I have an idea on how to implement this, so I will add this to my plans. Thanks for the suggestion!
SingletonSean cheers for replying man. I’m working on something at the moment which is how I found your channel. Watching the series from scratch now as really enjoying it. The method I’m using atm is binding the users Id to the PasswordBox tag property and passing the box as a parameter. Wasn’t overly happy with it but it works lol
Hi there! First of all congrat you for these amazing videos! The only point that I don´t understand quite well are why would you use a factory for each and every of the viewmodels...I was wondering if you could do a quick video explaining why would you use Factories and how could that interact with the singleton or scoped injection of them. Thanks in advance
Hi, I was wondering if you have any plans to add Groups (Authorization) to the program now that you have (Authentication). Like an Admin or User Group. Thanks for another great episode!
Sean - this was a great video. Will you be showing us how to use the authentication state in the rest of the application? I'm still trying to figure out how to get my MainViewModel to access the data that's inside the Authenticator.
Hi Abdullah, the dependency property snippet should be built-in to Visual Studio. If not, you can snag it here: gist.github.com/emoacht/296c02de3af91d1334dd
Hey Sean! You are posting really great content. I've seen other videos on WPF and MVVM framework but until now I'm understanding everything. I wanted to ask you something that is not related to this topic but to WPF. Have you ever develop an app that has like a graphical view to which the user can interact? For example, drawing lines or polygons with interactions. If you have, which libraries do you recommend? Cheers, Sergio Camacho
Hey Sergio, I haven't done too in depth with drawing, mostly just because I haven't had a use case for it yet. I have done a lot with drag and drop recently though, which is something I would like to do a video on. Perhaps I could incorporate some drawing with that. As for libraries, it seems like WPF has a really nice API for drawing and graphics, so I've just been using built in support. It would be nice to find a really easy to use library though. Thanks for the suggestion!
I am so excited about this, I've heard about unit testing and never knew where to start, and now I've done it and can start contemplating how to integrate it into my other work. Thank you!
Great video. I think that they are just the right length. Some video tutorials are so long that they are exhausting to watch in one sitting and once I leave its tough to come back and try to find where you were and all that. But your videos can be consumed in one sitting and I can save the next video for the following day without breaking up the lesson.
Just thought I'd be specific about what I like about them. Maybe it would help. Keep going.
Thanks for the feedback MSon! This has always been something I've wondered about. Personally, I prefer watching videos under 20 minutes, so I can definitely understand the fatigue with watching long videos. I sense that other people have similar preferences, so I rarely make 20+ minute videos anymore.
Hi,thank u for your videos, do you implement roles in next videos?
Hey Комиль, this would be a great application to implement roles for! Thank you for the suggestion. I will add this to the list of things to add down the road.
Hi, Why you have separate AuthenticationService and Authenticator? I see that Authenticator has extra functionality (CurrentAccount), this is all the reason? The second question is why the Authenticator is in the WPF project instead of the domain project?
Hey Sean, I love this series and have been following it to make some bug tracking software for my development portfolio. I'm a bit confused about why you made a new IAuthenticator interface that has its own Login and Register methods that just use the Login and Register methods from the IAuthenticationService interface that already exists? I know there is probably a reason, but why not just use the IAuthenticationService?
Another excellent contribution!
Hi, Thanks for wonderful content, I wonder if you could also implement Roles for users, like a user, superuser, Admin. block access to views depending on roles. thank you.
Hey Gajaruban, many people have requested roles, so I feel obligated to look at implementing them in the future, haha.
Hi Sean, thank you for the tutorial, i just wanna know why we should never let an async void out of a try catch, what's the point ?
Hey Engineer-Development, if an async void throws an exception, it will crash the application. Additionally, any function that calls the async void will not be able to catch the exception. Preventing async voids from throwing any exceptions is the safest solution. Good question!
@@SingletonSean oh ok, so if it was an async method but that returns a datatype, that would be easier to debug and prevents app crashing or it's because of the fact that it is async?
Hello I am trying to understand and build Application and implement "new feautres" according to my possibilities. How can I implement that the currently logged in user is displayed (e.g. in the upper left corner) of the Home, Buy or Sell view / Main window? What would I have to do to add a logout or change user button.
A textblock with a binding to the currentUser's username. Logout button would probably just be a button hooked up to a command that calls Logout, and switching users is really just logging out then going to the log in view.
Hey - really like the content. Wondering if there was a more MVVM friendly approach for the password section? Was trying to avoid doing code behind if possible
Hey James, I'm the same way as you with avoiding code behind haha. It's not always terrible, but for this I would definitely prefer a bindable password box rather than relying on command parameters. I have an idea on how to implement this, so I will add this to my plans. Thanks for the suggestion!
SingletonSean cheers for replying man. I’m working on something at the moment which is how I found your channel. Watching the series from scratch now as really enjoying it.
The method I’m using atm is binding the users Id to the PasswordBox tag property and passing the box as a parameter. Wasn’t overly happy with it but it works lol
Hey amazing work! Waiting for next episode !!!!
Thanks konrad, glad you're enjoying! More on the way.
Hi there! First of all congrat you for these amazing videos! The only point that I don´t understand quite well are why would you use a factory for each and every of the viewmodels...I was wondering if you could do a quick video explaining why would you use Factories and how could that interact with the singleton or scoped injection of them.
Thanks in advance
Hi, I was wondering if you have any plans to add Groups (Authorization) to the program now that you have (Authentication). Like an Admin or User Group. Thanks for another great episode!
Sorry, I see you already answered the Groups/Roles question below. Here's another vote for that idea! :-)
I think he could do that by adding that after the fact doing a call to see if a certain group / role is assigned to the username / user id
Sean - this was a great video. Will you be showing us how to use the authentication state in the rest of the application? I'm still trying to figure out how to get my MainViewModel to access the data that's inside the Authenticator.
Hey Noah, definitely! And very soon too.
Thank for this great content. Would you be able to share the code snippet for Dependency Property with us?
Hi Abdullah, the dependency property snippet should be built-in to Visual Studio. If not, you can snag it here: gist.github.com/emoacht/296c02de3af91d1334dd
@@SingletonSean
Awesome. Thanks :)
great content
Hey Sean!
You are posting really great content. I've seen other videos on WPF and MVVM framework but until now I'm understanding everything. I wanted to ask you something that is not related to this topic but to WPF. Have you ever develop an app that has like a graphical view to which the user can interact? For example, drawing lines or polygons with interactions. If you have, which libraries do you recommend?
Cheers,
Sergio Camacho
Hey Sergio, I haven't done too in depth with drawing, mostly just because I haven't had a use case for it yet. I have done a lot with drag and drop recently though, which is something I would like to do a video on. Perhaps I could incorporate some drawing with that. As for libraries, it seems like WPF has a really nice API for drawing and graphics, so I've just been using built in support. It would be nice to find a really easy to use library though. Thanks for the suggestion!
like the content bud
nice work !!
NICE SONG
thanks following