I personally feel the universities themselves should pay you for making such quality content accessible to computer science students all over the world! God bless!
0:00 - Intro 1:19 - Demo application walk through (WinForms) 3:18 - Code behind the demo app 18:28 - Event: Button click 21:21 - Creating and Invoking custom Event 26:35 - Event " ?.Invoke() " explained 30:00 - Listening to and writing code for the Event 34:00 - Creating the custom Event: Event in action and recap 37:12 - Event argument information: debugging 38:42 - Creating Another custom Event (overdraft event) 43:28 - Listening for the event in multiple places 46:33 - Removing Event Listeners form memory 49:00 - EventHandler: Passing class for T 53:39 - why not to use "public set" for properties 59:25 - Exception when to use public set 1:06:13 - Summary
I've been coding for decades. WPF since about 2012. Always under pressure to get code delivered and make sure I don't break code I already have. I have rarely had time to become expertly proficient in most of the things I code and oh yeah.. xaml is my nemesis. I've got a few weeks of time before the next big project begins and I want to step up my game each time I start a new app as there won't be a lot of time for massive changes along the way. Corey's tutorials are so helpful for me to gather my wits and learn more before I begin again. Thanks Corey.
i dont mean to be so off topic but does anyone know of a method to get back into an instagram account..? I somehow lost my password. I would appreciate any assistance you can give me
Greatest teacher ever! I have listened you and i went on step 1 instead on going on step 3 or 4 as you said in your first video of Getting started with C# even if i knew something about C# but i was rusty. Everything is understandable and personally i receive knowledge very easy. PS: I am really glad that every few days you have 1k more subscribers, you really deserve it ! Every here and when i recommend you to my friends or people that are interested in programming. Keep up the good work, you are rare diamond on RUclips. Best regards !
27:11 "There's no point of saying if something new happen, if no one cares" well that's one sentence I'll remember forever :) great as usual Tim, it's nice to refresh to my knowledge about C#, even if it's my everyday, used at work language. One video a day makes it easier to remember all these amazing features and their concepts.
A Question : You mentioned that when passing an object through the event; that the setters in the properties of that object need to be private to prevent every listener from modifying them. My question is; when passing the object, isn't it a copy of the object?(by value) and thus the changes on that object by the listeners shouldn't affect the original object? Maybe i missunderstod something. Thank you for your valuable knowledge!
Thank you! As for the object copying, objects are actually never copied. The variables hold a reference to the object so when we pass an object into a method (or event), we are passing the reference even though the parameter is "by value" by default.
Great content man. I'm interviewing for a senior .NET developer position next week and am watching some of your content on things I haven't ran into in my daily work and your content is super helpful and informative. Good stuff dude. People like you change so many lives by helping them gain marketable skill sets in the real world.
Good luck with the interview! Please let us know how it goes. Check out Tim's Dev Questions videos about interviewing to help you get in the right frame of mind - ruclips.net/user/IAmTimCoreysearch?query=interview
@@tomthelestaff-iamtimcorey7597 It turned out not to be a technical interview but rather a more conversational interview. I think spending hours by myself in the dark looking at code may have ended up being more of a detriment than anything else hahaha. It did go well though; waiting to hear back but it was very recently so here's hoping.
I just stopped by this video to refresh myself on some concepts with events. I don't comment on every video of yours because I'd be pretty much repeating myself every time but: I started learning to code last October. I settled on learning C# somewhat arbitrarily (originally I wanted to have a go at making video games in Unity), and quickly realised that programming was something I was passionate about. Thanks to you, in less than a year I have become confident in a whole host of topics, from building ASP.NET Core (Razor & MVC) web apps, carrying out data access, and unit testing my code; to designing applications with a clean decoupled architecture and a focus on separation of concerns. Not only that, I am now starting to be offered Software Development jobs (something I thought would be impossible without a Computer Science degree) and feel like not only do I have a decent knowledge of these topics but I know what to do and where to look to improve on that knowledge! So, yes, I just wanted to say many thanks for uploading these videos! I have subscribed to your mailing list - and I direct friends/anyone interested to your channel and website when they ask about C#. Absolutely stellar job - you have literally opened up a career for me and for that I am extremely grateful! I look forward to seeing what you continue to produce! - Matt
Thanks Tim. Best explanation of C# Events. I have checked Pluralsight, Linkedin Learning and several online content for C# events and this is by far the best explanation of how practically to use events.
Hi Tim, I've been a subscriber to your channel for a while now, but obviously only since after the publication of this video. I had reached a point in my current project where I felt I could probably achieve my target through exceptions, but couldn't work out how to do it. I looked at a load of text tutorials on-line, each more overly complicated than the last. Then I found your video here. It was super easy to follow, really clearly explained, and I managed to implement exceptions in my own project, alongside watching you explain it. Thank you very much :)
Hi Tim, thank you very much for this, I watched the other videos on Events and now this one, and NOW I have a really good understanding how events work and how to reduce the linear flow of my applications through events. I really did not understand how this worked until now. Books or other youtube videos fall way short of the way you have designed and presented this demo application to show us how to use events in a real world application. Also, grateful for the source code that you supply with these videos so that we can learn by doing. I hear, I forget; I see, I remember; I do, I understand!
Tim Corey your videos are amazing I love the free content so much a bought a few of your courses during the black Friday sale. Thank you I have learned so much from your content!
Tim Corey, great job on explaining events and showing how to add custom events. I love C# and use it everyday. This video gave me some new info that will be very helpful!! Thanks.
IAmTimCorey Even though the other tutorials were in Russian) Imagine how good this tutorial has to be if English is my 3’rd language))) Imagine how bad is my English but still i had no problems with understanding how events work)
Mr. Corey, your C# channel is perhaps my most favorite! By the way, will you ever make a video on the Bitmap class (because there are not sufficient videos on RUclips covering image manipulation with C#)? Perhaps image manipulation is not a topic that is strictly relevant to the engineering side of things, but it's still useful for UI/UX!
Hi Cory, Really enjoyed your vids and have learned alot. I have used c before but now I am looking into the interface to my windows laptop. At the present time I program my own devices and enjoy learning programing. I only write my own files at this time. for my stuff. Thanks again, Len
Hey Tim, Great video again. I've always had trouble wrapping my head around the whole 'events' thing. In the past I've read some pretty compicated stuff, but that was all explained from the point, which is still true of course, that it all starts at the point where you get to learn about delegates, after which it gets increasingly complicated. For me, that is. But your video made it much clearer. Just to be shure I'm doing the unsubscribing of the events the proper way, this is the code I devised for that purpose: private void Transactions_FormClosing(object sender, FormClosingEventArgs e) { _customer.CheckingAccount.OverdraftEvent -= CheckingAccount_OverdraftEvent; } I had to go for the _customer, since customer is a function parameter of the constructor and therefore not accessible outside of that. private void Dashboard_FormClosing(object sender, FormClosingEventArgs e) { customer.CheckingAccount.TransactionApprovedEvent -= CheckingAccount_TransactionApprovedEvent; customer.SavingsAccount.TransactionApprovedEvent -= SavingsAccount_TransactionApprovedEvent; customer.CheckingAccount.OverdraftEvent -= CheckingAccount_OverdraftEvent; } Or is it better to do this inside the _FormClosed event? BTW, is there a way to check if there are memory leaks should one omit this sort of code? Thanks, Peter
The FormClosing event is the place to do it. You don't really need to do it in your main form, since when that form closes the application closes but that all looks right. As for checking for memory leaks, I'll be doing a video on that in the future. You can use a profiler to track your usage.
Question about removing event listeners: you mentioned on a form’s Close event; can you also do it as part of the form’s destructor, since a form is a class?
Thanks a lot Tim. One question please, If the part we clean up the event listeners by -= the handlers is so standard, why didn’t Microsoft do for us? I mean like using statement. Thanks again.
I love your way of teaching, it's very simple and practical, but in my opinion, you should put your video about event after delegate. Event and delegate are not only very closely related, under the hood delegate is the foundation for event and explaining event - again in my opinion only - without mentioning delegate first is harder and easier to get confuse
I understand. The reason I usually switch the order, though, is because people are used to events. Doing something when a button is clicked is usually one of the first things a developer learns (not my recommended order). So, wrapping your mind around events is easier than delegates. Once you know how events work, you can expand to delegates are easier to understand (which is a good thing since they are complicated).
@@IAmTimCorey thank you for your response. Wow that's kind of weird to learn event like that, because the first question that would pop up in my mind is: "what is that EventHandler thing" but I can see why event would come up so early for window app developer. Thank you again
Thank you Tim for making C# Events so easy to understand that C# beginner can understand. I had a confusion though: Am I right in saying that, removal of Events such as recordTransactionsButton_Click, errorMessage_Click is taken care of by Visual Studio but the events such as TransactionApprovedEvent, OverdraftEvent that we create must be removed by us. Also, where in the code should I put customer.CheckingAccount.OverdraftEvent -= CheckingAccount_OverdraftEvent; to remove CheckingAccount_OverdraftEvent?
Hello Tim, I started watching your videos recently and they have been very good. I went to your patreon page and was looking through the Tiers. I think you have a small typo on the first Tier for $1: " Did you know paying just $1/month provides me with more income than RUclips ads do for all of your views? So if you are wondering if this matters, is absolutely does. " I assume the last three words of that string are supposed to be "it absolutely does" instead of "is absolutely does". Just thought you would like to know. Thanks for the videos!
Nice to know about events. I guess we can use it whether windows form or wpf but i dont feel comfortable with windows forms. Drag and drop feels just not corret. Anyways, everything will be more clear on user interface section :))
I started on WinForms and doubting what to do next. I understand the feeling of it not being correct, but the WinForms designer is so easy to use for starters..
As far as I've understood it and from my experience in other languages, events are mostly used in GUI contexts, like button clicks and similar. Would you say it is wrong or bad practice to use events for other purposes than GUI, more specifically for monitoring the data on the model side of an application? For example, my current practice project is a small game. I'm thinking that using events to listen to a character's health points can then invoke an event CharacterDiedEvent and modify other classes accordingly, for example. So I will use the event purely for the model and not for the view.
So, I know this is a month late, but I'll try my best to explain how you could consolidate this code. Both Account Event functions do very similar logic with very similar data types. Each resets and fills it's list boxes, and change a Text Element's value. What we could do is write another function called something like UpdateFormWithNewTransactionInfo with parameters of (ListBox box, Label label, Account account). Then we'll just put in generic code and pass in the data we actually want to change as parameters. Think something like this: private void UpdateFormWithNewTransactionInfo(ListBox box, Label label, Account account) { box.DataSource = null; box.DataSource = account.Transactions; label.Text = string.Format("{0:C2"}, account.Balance); }
Hi Tim! I have a question about the first event - TransactionsApprovedEvent. Can I replace this event with a Binding Source? I mean I could declare a new Binding Source and assign it to our transactions list from Account Class. Will it work? Of course, I would like thank you for this video. Your way of explaining C# is always awesome :)
Because that public get would get you a reference of the list and you can alter that list in any way you want including adding and removing items. The private set only prevents you from exchanging the list reference in the property. A ReadOnlyList on the other hand makes the elements IN the list readonly as well, so you can get an element at an index but not set.
Hi Tim, May I ask why we need to use IReadOnlyList for Transactions? This property (Transactions) do not have set for outside of class to change the value.
To prevent another programmer in the bank accidentally/intentionally modifying a list that comes from that class. It is not powerful protection by itself (because you can make anew list with the same contents) against error/fraud but once you combine it with the full suite of fraud/error controls at the bank it becomes more useful.
@@michaelnurse9089 Ok yours makes sense but makeing a property type just IList ( instead of IReadOnlyList) and returning _transactions.AsReadOnly () in getter will not be sufficient protection. I mean if we return _transaction.AsReadOnly() in getter, why we should use IReadOnlyList type rather than just regular IList ???
I think I'll just unsub from other coding channels. Consistently your tutorials allow me to understand and use the concepts than other tutorials, whether they are longer or shorter. Grateful!
@@IAmTimCorey thank you sir but i would rather that you consider making a video about this topic because you know how to explain things and make it easy to understand fankly i read a ton of articles but i couldn't get what i need especially the best practice when it comes to this problem
Hi Tim! I highly appreciate you for providing us such a valuable content. I have a question about Events. For me it looks that everything you done by implementing events in this movie, may be achieved by implementing just appropiate plain functions. Is it true? Anyway, why really we should use events? I understand how they works, but i'm sure that i wouldn't be able to decide when use events, and when not in my code.
Events allow you to act in a disconnected manner. Yes, you could just create a function but then the event caller would need to know about a method on the event receiver. That creates a tight coupling. Think about Windows Forms. When you click a button, you want something to happen, right? If that button click didn't fire an event but it called a method, how would you add your code later? Microsoft created the button. They would have to know which method(s) to call when they build the button but your methods weren't created until years later.
That way exposes the EventHandler as a public field, which would allow it to be overwritten instead of just subscribed to. It is considered a dangerous practice: stackoverflow.com/a/46824847/733798 Good question.
very informative and helpful. in the start to finish course, you always used the wiredup() method, does that means we can call an event there as well or eventhandler will not work there. thanks for all the good work that you put in your videos and they really are helpful.
Tim I know you are a huge fan of using Windows when building your apps. Since the release by Microsoft dotnet core for all 3 platforms now with a little work you can not only build and run your apps within either OSX or Linux. Then on that subject build an app using the built in API with Angular. Do you have any further plans for this?
I'm currently working on a full application course where the application is built fully in .NET Core (a web-based helpdesk system). I'll be building on Windows because that is what I have but I'll surely accept the donation of a new MacBook to do videos on :-) Just note that while .NET Core runs on any platform, WinForms, WPF, and UWP do not so they can only be built in Windows and run on Windows. .NET Core 3.0 is bringing .NET Core to WinForms and WPF but they still won't run on anything but Windows (and you can't build them on anything but Windows as well). There is a benefit to making them .NET Core but it isn't about cross-platform.
Hello Tim! In this case, which one is the Publisher and which one is the Subscriber? Is the publisher in the UI or is it the one with the .Invoke() method? And the subscriber is the one which is called with the Invoke() method?
The communication between the two Forms and the customer class can also be done by adding bindings to the Form controls. Would you prefer to use data binding or to set up events? Thanks, Tim!
Awesome stuff! I have a question, how could you trigger and event in the background when for example gamepad controller was connected or disconnected? I do not know where to handle the event listener that it would check if the controller is connected or not! thanks in advance! BR
Hey Tim... Just had a little query... I still don't have any idea of WPF and even Winforms... So could you please tell me how I could practice the events? I admit that it's possible to practice with the demo, but I want to apply it once myself....
I can't specifically answer that questions, but I can point you to Tim 'Intro to WPF' - ruclips.net/video/gSfMNjWNoX0/видео.html Please consider checking it out!
You can create console applications and try things out. Events work fine in console. Make them trigger when something is near full - like a list or a game level is almost complete or something like that.
I personally feel the universities themselves should pay you for making such quality content accessible to computer science students all over the world! God bless!
Thank you for the kind words.
He is literally the best teacher for computer science ever. I mean he still replies to my comments. He is the first person i donated some money too.
0:00 - Intro
1:19 - Demo application walk through (WinForms)
3:18 - Code behind the demo app
18:28 - Event: Button click
21:21 - Creating and Invoking custom Event
26:35 - Event " ?.Invoke() " explained
30:00 - Listening to and writing code for the Event
34:00 - Creating the custom Event: Event in action and recap
37:12 - Event argument information: debugging
38:42 - Creating Another custom Event (overdraft event)
43:28 - Listening for the event in multiple places
46:33 - Removing Event Listeners form memory
49:00 - EventHandler: Passing class for T
53:39 - why not to use "public set" for properties
59:25 - Exception when to use public set
1:06:13 - Summary
Thanks! I added it to the description.
I've been coding for decades. WPF since about 2012. Always under pressure to get code delivered and make sure I don't break code I already have. I have rarely had time to become expertly proficient in most of the things I code and oh yeah.. xaml is my nemesis. I've got a few weeks of time before the next big project begins and I want to step up my game each time I start a new app as there won't be a lot of time for massive changes along the way. Corey's tutorials are so helpful for me to gather my wits and learn more before I begin again. Thanks Corey.
Excellent!
i dont mean to be so off topic but does anyone know of a method to get back into an instagram account..?
I somehow lost my password. I would appreciate any assistance you can give me
WHen i found ur channel i felt like i've won in lottery. Such nice and clear explanations, really love it, thank u very very much, Tim. U r doing nice
I am glad you found it so helpful.
Hi, Tim. You are the best C# instructor.
I appreciate the kind words.
For sure he is ❤️❤️
Greatest teacher ever! I have listened you and i went on step 1 instead on going on step 3 or 4 as you said in your first video of Getting started with C# even if i knew something about C# but i was rusty. Everything is understandable and personally i receive knowledge very easy.
PS: I am really glad that every few days you have 1k more subscribers, you really deserve it ! Every here and when i recommend you to my friends or people that are interested in programming. Keep up the good work, you are rare diamond on RUclips. Best regards !
I am glad it has been helpful. Thanks for recommending the channel.
27:11 "There's no point of saying if something new happen, if no one cares" well that's one sentence I'll remember forever :) great as usual Tim, it's nice to refresh to my knowledge about C#, even if it's my everyday, used at work language. One video a day makes it easier to remember all these amazing features and their concepts.
I'm glad it made an impression.
Thanks
A Question :
You mentioned that when passing an object through the event; that the setters in the properties of that object need to be private to prevent every listener from modifying them. My question is; when passing the object, isn't it a copy of the object?(by value) and thus the changes on that object by the listeners shouldn't affect the original object? Maybe i missunderstod something. Thank you for your valuable knowledge!
Thank you! As for the object copying, objects are actually never copied. The variables hold a reference to the object so when we pass an object into a method (or event), we are passing the reference even though the parameter is "by value" by default.
Thanks!
Thank you!
Great content man. I'm interviewing for a senior .NET developer position next week and am watching some of your content on things I haven't ran into in my daily work and your content is super helpful and informative. Good stuff dude. People like you change so many lives by helping them gain marketable skill sets in the real world.
Good luck with the interview! Please let us know how it goes. Check out Tim's Dev Questions videos about interviewing to help you get in the right frame of mind - ruclips.net/user/IAmTimCoreysearch?query=interview
@@tomthelestaff-iamtimcorey7597 It turned out not to be a technical interview but rather a more conversational interview.
I think spending hours by myself in the dark looking at code may have ended up being more of a detriment than anything else hahaha.
It did go well though; waiting to hear back but it was very recently so here's hoping.
@@bleepbloop6303 Thanks for the update. Let us know!
I just stopped by this video to refresh myself on some concepts with events. I don't comment on every video of yours because I'd be pretty much repeating myself every time but: I started learning to code last October. I settled on learning C# somewhat arbitrarily (originally I wanted to have a go at making video games in Unity), and quickly realised that programming was something I was passionate about.
Thanks to you, in less than a year I have become confident in a whole host of topics, from building ASP.NET Core (Razor & MVC) web apps, carrying out data access, and unit testing my code; to designing applications with a clean decoupled architecture and a focus on separation of concerns. Not only that, I am now starting to be offered Software Development jobs (something I thought would be impossible without a Computer Science degree) and feel like not only do I have a decent knowledge of these topics but I know what to do and where to look to improve on that knowledge!
So, yes, I just wanted to say many thanks for uploading these videos! I have subscribed to your mailing list - and I direct friends/anyone interested to your channel and website when they ask about C#. Absolutely stellar job - you have literally opened up a career for me and for that I am extremely grateful! I look forward to seeing what you continue to produce! - Matt
This is why I am passionate about my work. I love hearing these stories. Thank you for sharing your journey!
Good job keeping it DRY! Ha, sorry, couldn't help myself :)
Thanks Tim. Best explanation of C# Events. I have checked Pluralsight, Linkedin Learning and several online content for C# events and this is by far the best explanation of how practically to use events.
Thanks! I appreciate the kind words.
Great teaching. For others who think Tim's videos r long, who come here to pick quick things, no this is organic teaching, not junk food learning.
Thank you!
There's a middleground. 17 minutes in and this guy still hasn't said anything.
Hi Tim, I've been a subscriber to your channel for a while now, but obviously only since after the publication of this video. I had reached a point in my current project where I felt I could probably achieve my target through exceptions, but couldn't work out how to do it. I looked at a load of text tutorials on-line, each more overly complicated than the last. Then I found your video here. It was super easy to follow, really clearly explained, and I managed to implement exceptions in my own project, alongside watching you explain it. Thank you very much :)
Awesome! I'm glad it was so helpful.
You're such a good teacher. Just wanted to let you know. Keep it up
I appreciate that!
Thank you very much for an explanation of the very details of this pretty complicated concept Mr. Corey!
You are welcome.
This video is really incredible, as always. Thank you Tim.
Hi Tim, thank you very much for this, I watched the other videos on Events and now this one, and NOW I have a really good understanding how events work and how to reduce the linear flow of my applications through events. I really did not understand how this worked until now. Books or other youtube videos fall way short of the way you have designed and presented this demo application to show us how to use events in a real world application. Also, grateful for the source code that you supply with these videos so that we can learn by doing. I hear, I forget; I see, I remember; I do, I understand!
I am glad it was helpful.
Tim Corey your videos are amazing I love the free content so much a bought a few of your courses during the black Friday sale. Thank you I have learned so much from your content!
Awesome! I'm glad have learned a lot from my content.
Dear Tim, once again, thank you very much.
You are welcome.
Quality! beautiful teaching
Thank you!
Very helpful course with nice n clear explanation. Many thanks Tim.
Very welcome
I take it slow and spend my two day for events. Now i understand whole thing. Perfect.
Great!
Tim Corey, great job on explaining events and showing how to add custom events. I love C# and use it everyday. This video gave me some new info that will be very helpful!! Thanks.
Glad it was helpful!
Thank you so much. I was struggling to make custom Events for so long. But with this VERY clear explanation , I can finally do it easily.
Glad it helped!
The best events tutorial i`ve ever seen. Beelive me i red and seen a lot of them, and couldn`t understand a damn thing. Thank you!
You are welcome.
IAmTimCorey Even though the other tutorials were in Russian) Imagine how good this tutorial has to be if English is my 3’rd language))) Imagine how bad is my English but still i had no problems with understanding how events work)
I'm actually falling in love with this stuff
Excellent!
Very good, this es the only one that so far Made me undertand about event handlers, I watch it every time I want to implement one
I am glad you found it useful.
Thank you very much I was so confused until I watched this
You are welcome.
Thanks alot Tim, keep up the great work, you are fantastic.
Thanks for trusting Tim.
Thanks TIm on another great tutorial. This is so simple and consise explanation of C# events.
Cheers
I'm glad you enjoyed it.
Thank you for this video, it's really nicely put together.
I also like you clear calm way of speaking :)
Subbed
You are most welcome. Thanks for watching.
This is just an amazing explanation with lots of tips, thanks a lot, Tim!!
You are welcome.
Another great video. Now I understand events better. Thanks Tim!
Excellent.
Subscribed and liked. The video is long but worth. You did make it coherent and precise. Again thank you.
You are most welcome. Thanks for watching.
Thanks for sharing your knowledge
You are welcome.
Thanks for video. It really help me understand events.
You are welcome.
Thanks Tim, now more comfortable to use events in our code.
Great!
You are the best at explaining! Thank you so much!
Happy to help!
Brilliant job Tim. Thanks a lot for sharing it!
Thank you!
Excellent teaching.
Thanks!
Great video Tim, very simple to understand. Thanks!
You are welcome.
Mr. Corey, your C# channel is perhaps my most favorite! By the way, will you ever make a video on the Bitmap class (because there are not sufficient videos on RUclips covering image manipulation with C#)? Perhaps image manipulation is not a topic that is strictly relevant to the engineering side of things, but it's still useful for UI/UX!
I will add it to the list. Thanks for the suggestion.
An hour long, but totally worth it.
Great!
Another great video. You are super. Thanks for the Video Tim.
You are welcome.
Hi Cory, Really enjoyed your vids and have learned alot. I have used c before but now I am looking into the interface to my windows laptop.
At the present time I program my own devices and enjoy learning programing. I only write my own files at this time. for my stuff. Thanks again, Len
You are welcome.
Great video as always Tim!
Thanks!
Thanks a million for such quality education! You're awesome!
Thank you!
Thank you for all your videos, they've been quite helpful.
You are most welcome. Thanks for watching.
Tim, once again - thank you! Cool lesson.
You are welcome.
⭐️⭐️⭐️⭐️⭐️ video
Thanks!
Thank you! I have reinforced my Events handling knowledge.
I'm glad it reinforced some things for you.
You are the best! Thanks you so much :) Really helped me understand events a bit better!
Glad it helped!
Hey Tim,
Great video again. I've always had trouble wrapping my head around the whole 'events' thing. In the past I've read some pretty compicated stuff, but that was all explained from the point, which is still true of course, that it all starts at the point where you get to learn about delegates, after which it gets increasingly complicated. For me, that is. But your video made it much clearer.
Just to be shure I'm doing the unsubscribing of the events the proper way, this is the code I devised for that purpose:
private void Transactions_FormClosing(object sender, FormClosingEventArgs e)
{
_customer.CheckingAccount.OverdraftEvent -= CheckingAccount_OverdraftEvent;
}
I had to go for the _customer, since customer is a function parameter of the constructor and therefore not accessible outside of that.
private void Dashboard_FormClosing(object sender, FormClosingEventArgs e)
{
customer.CheckingAccount.TransactionApprovedEvent -= CheckingAccount_TransactionApprovedEvent;
customer.SavingsAccount.TransactionApprovedEvent -= SavingsAccount_TransactionApprovedEvent;
customer.CheckingAccount.OverdraftEvent -= CheckingAccount_OverdraftEvent;
}
Or is it better to do this inside the _FormClosed event?
BTW, is there a way to check if there are memory leaks should one omit this sort of code?
Thanks,
Peter
The FormClosing event is the place to do it. You don't really need to do it in your main form, since when that form closes the application closes but that all looks right. As for checking for memory leaks, I'll be doing a video on that in the future. You can use a profiler to track your usage.
Question about removing event listeners: you mentioned on a form’s Close event; can you also do it as part of the form’s destructor, since a form is a class?
This video really helped me a lot, Thank you so much!
You are welcome.
Thanks a lot Tim. One question please, If the part we clean up the event listeners by -= the handlers is so standard, why didn’t Microsoft do for us? I mean like using statement. Thanks again.
I love your way of teaching, it's very simple and practical, but in my opinion, you should put your video about event after delegate.
Event and delegate are not only very closely related, under the hood delegate is the foundation for event and explaining event - again in my opinion only - without mentioning delegate first is harder and easier to get confuse
I understand. The reason I usually switch the order, though, is because people are used to events. Doing something when a button is clicked is usually one of the first things a developer learns (not my recommended order). So, wrapping your mind around events is easier than delegates. Once you know how events work, you can expand to delegates are easier to understand (which is a good thing since they are complicated).
@@IAmTimCorey thank you for your response. Wow that's kind of weird to learn event like that, because the first question that would pop up in my mind is: "what is that EventHandler thing" but I can see why event would come up so early for window app developer. Thank you again
I Have All Of Your Videos and I Like Your C# Skills
Thank you!
You are making my code better. Thanks.
Glad to hear that!
I like the new event shorthand notation.
It is convenient at times.
Great tutorial. Would you recommend this approach in a blazor client side app?
Using events? Sure.
Thank you Tim for making C# Events so easy to understand that C# beginner can understand. I had a confusion though:
Am I right in saying that, removal of Events such as recordTransactionsButton_Click, errorMessage_Click is taken care of by Visual Studio but the events such as TransactionApprovedEvent, OverdraftEvent that we create must be removed by us.
Also, where in the code should I put customer.CheckingAccount.OverdraftEvent -= CheckingAccount_OverdraftEvent; to remove CheckingAccount_OverdraftEvent?
9:40 shouldn't balance be greater than or equal to amount?
10:12 welp, nvm.
Great video, keep it up.
Thank you!
Great video on events.
Thanks!
Hello Tim, I started watching your videos recently and they have been very good.
I went to your patreon page and was looking through the Tiers. I think you have a small typo on the first Tier for $1:
"
Did you know paying just $1/month provides me with more income than RUclips ads do for all of your views? So if you are wondering if this matters, is absolutely does.
"
I assume the last three words of that string are supposed to be "it absolutely does" instead of "is absolutely does".
Just thought you would like to know. Thanks for the videos!
Thanks for the heads up. I fixed it.
Nice to know about events. I guess we can use it whether windows form or wpf but i dont feel comfortable with windows forms. Drag and drop feels just not corret. Anyways, everything will be more clear on user interface section :))
I started on WinForms and doubting what to do next. I understand the feeling of it not being correct, but the WinForms designer is so easy to use for starters..
You can use Events in any part of C#, not just in the user interface.
Great tutorial
Thanks!
Great video, thank you for your work!
You are welcome.
As far as I've understood it and from my experience in other languages, events are mostly used in GUI contexts, like button clicks and similar. Would you say it is wrong or bad practice to use events for other purposes than GUI, more specifically for monitoring the data on the model side of an application?
For example, my current practice project is a small game. I'm thinking that using events to listen to a character's health points can then invoke an event CharacterDiedEvent and modify other classes accordingly, for example. So I will use the event purely for the model and not for the view.
If match your requirements, why not?
No, it isn't bad practice. Events are used for a lot more than just GUIs.
Event driven programming is used as a design practice for decoupling, publish/subscribe design pattern...from what I've read.
Dude thank you so much!
You are welcome.
33:50 I couldn't think of a way to fix the duplication, can you briefly explain what would you do here to fix it?
So, I know this is a month late, but I'll try my best to explain how you could consolidate this code. Both Account Event functions do very similar logic with very similar data types. Each resets and fills it's list boxes, and change a Text Element's value. What we could do is write another function called something like UpdateFormWithNewTransactionInfo with parameters of (ListBox box, Label label, Account account). Then we'll just put in generic code and pass in the data we actually want to change as parameters. Think something like this:
private void UpdateFormWithNewTransactionInfo(ListBox box, Label label, Account account) {
box.DataSource = null;
box.DataSource = account.Transactions;
label.Text = string.Format("{0:C2"}, account.Balance);
}
Thank you so much!
You are welcome.
Thanks in a million.
You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. You're welcome. ...
I strive to be as good as tim corey
He sets a high bar!
Hi Tim!
I have a question about the first event - TransactionsApprovedEvent. Can I replace this event with a Binding Source? I mean I could declare a new Binding Source and assign it to our transactions list from Account Class. Will it work?
Of course, I would like thank you for this video. Your way of explaining C# is always awesome :)
Cleaning and unsubscribing events I find the most challenging to avoid memory leak scenarios.
Yep, they are challenging.
@@IAmTimCorey I got caught in my own events web once or twice 😂
6:30 why not just write public List transactions { get; private set; } ?
Because that public get would get you a reference of the list and you can alter that list in any way you want including adding and removing items. The private set only prevents you from exchanging the list reference in the property. A ReadOnlyList on the other hand makes the elements IN the list readonly as well, so you can get an element at an index but not set.
Max is correct.
Hi Tim, May I ask why we need to use IReadOnlyList for Transactions? This property (Transactions) do not have set for outside of class to change the value.
To prevent another programmer in the bank accidentally/intentionally modifying a list that comes from that class. It is not powerful protection by itself (because you can make anew list with the same contents) against error/fraud but once you combine it with the full suite of fraud/error controls at the bank it becomes more useful.
@@michaelnurse9089 Ok yours makes sense but makeing a property type just IList ( instead of IReadOnlyList) and returning _transactions.AsReadOnly () in getter will not be sufficient protection. I mean if we return _transaction.AsReadOnly() in getter, why we should use IReadOnlyList type rather than just regular IList ???
A possible topic for upcoming videos: The Art of Clean Code (obviously in C#). What you think?
That's definitely a possibility.
Great work!
Thanks!
We need a discord server for the audience of this channel so that we can question and discuss more.
That's not something I'm able to do at this time. One step at a time.
I think I'll just unsub from other coding channels. Consistently your tutorials allow me to understand and use the concepts than other tutorials, whether they are longer or shorter. Grateful!
I am glad my content has been so helpful to you.
great video as always, can you explain the reference leak caused by events?
Here you go: stackoverflow.com/a/4526840/733798
@@IAmTimCorey thank you sir but i would rather that you consider making a video about this topic because you know how to explain things and make it easy to understand fankly i read a ton of articles but i couldn't get what i need especially the best practice when it comes to this problem
Hi Tim!
I highly appreciate you for providing us such a valuable content. I have a question about Events. For me it looks that everything you done by implementing events in this movie, may be achieved by implementing just appropiate plain functions. Is it true? Anyway, why really we should use events? I understand how they works, but i'm sure that i wouldn't be able to decide when use events, and when not in my code.
Events allow you to act in a disconnected manner. Yes, you could just create a function but then the event caller would need to know about a method on the event receiver. That creates a tight coupling. Think about Windows Forms. When you click a button, you want something to happen, right? If that button click didn't fire an event but it called a method, how would you add your code later? Microsoft created the button. They would have to know which method(s) to call when they build the button but your methods weren't created until years later.
@@IAmTimCorey great example
at 25:01, what if we just write "public EventHandler RaiseTransactionApprovedEvent;"? The code seems to work, but what are the differences?
That way exposes the EventHandler as a public field, which would allow it to be overwritten instead of just subscribed to. It is considered a dangerous practice: stackoverflow.com/a/46824847/733798 Good question.
@@IAmTimCorey totally makes sense now! Thanks!
Thank you for this :)
My pleasure!
Hi Tim. Just found your video. Great work. Thanks. However, the link to source code is not working. Could you help me get the source code? Thanks.
I fixed it. It should work now.
@@IAmTimCorey thank you. I have received it.
very informative and helpful. in the start to finish course, you always used the wiredup() method, does that means we can call an event there as well or eventhandler will not work there. thanks for all the good work that you put in your videos and they really are helpful.
You are most welcome. Thanks for watching.
23:25 is when he actually gets to the events
There is a lot of setup to get through first. Context is important.
Thank you very much.
You are welcome!
Many thanks for this great tutorial. Can you tell me which font you use for the text editor?
The standard one. I'm not sure specifically but I didn't change it.
Tim I know you are a huge fan of using Windows when building your apps. Since the release by Microsoft dotnet core for all 3 platforms now with a little work you can not only build and run your apps within either OSX or Linux. Then on that subject build an app using the built in API with Angular. Do you have any further plans for this?
I'm currently working on a full application course where the application is built fully in .NET Core (a web-based helpdesk system). I'll be building on Windows because that is what I have but I'll surely accept the donation of a new MacBook to do videos on :-) Just note that while .NET Core runs on any platform, WinForms, WPF, and UWP do not so they can only be built in Windows and run on Windows. .NET Core 3.0 is bringing .NET Core to WinForms and WPF but they still won't run on anything but Windows (and you can't build them on anything but Windows as well). There is a benefit to making them .NET Core but it isn't about cross-platform.
Hello Tim! In this case, which one is the Publisher and which one is the Subscriber?
Is the publisher in the UI or is it the one with the .Invoke() method? And the subscriber is the one which is called with the Invoke() method?
The communication between the two Forms and the customer class can also be done by adding bindings to the Form controls. Would you prefer to use data binding or to set up events? Thanks, Tim!
I feel that for this particular task Events would work more smoothly.
It does depend on the scenario. An event could be the right way to go. Passing a form reference can also be an option.
Awesome stuff! I have a question, how could you trigger and event in the background when for example gamepad controller was connected or disconnected? I do not know where to handle the event listener that it would check if the controller is connected or not!
thanks in advance! BR
When talking about hardware, you would need to probably bring in external libraries to listen for those events.
Mr. Corey, could you please introduce a book for those who like to go deeper into these concepts of C# programming? Thank you so much
Hey Tim... Just had a little query... I still don't have any idea of WPF and even Winforms... So could you please tell me how I could practice the events? I admit that it's possible to practice with the demo, but I want to apply it once myself....
I can't specifically answer that questions, but I can point you to Tim 'Intro to WPF' - ruclips.net/video/gSfMNjWNoX0/видео.html Please consider checking it out!
You can create console applications and try things out. Events work fine in console. Make them trigger when something is near full - like a list or a game level is almost complete or something like that.
@@tomthelestaff-iamtimcorey7597 Thanks!
@@michaelnurse9089 Thank you so much... That's a great idea to work with!!!
hi, Tim.
Good video. But what is Event accessors ("add" and "remove") ?
Add allows us to add an event endpoint and remove allows us to remove it.