there is a callback in any delegate using begininvoke() which will also make the function run in different thread never the less You did a great work thank you
Imagine that you have Yes/No UI Window witch you wanna reuse in your app and buttons should do different things every time.So you can call your ShowWindow() function and as a parameters you can pass the addresses(functions) you want to be executed when Yes or No is clicked. Something like this: ShowWindow(OnYesCallback,OnNoCallback)
There is no difference in output with or without callback? So what's really happening? Is it just theory to understand that using delegate, our compiler will be doing other tasks rather than just waiting for a task to complete?
I really wasn't getting how delegates and callbacks worked but your video was simple and easy to understand. Thank you!
Thanks! I didn't see your reply until now. Glad it helped.
thanks for the video. one thing, people who look for this king of subjects - know basic things like open new project or console.read....
Why did you copy and paste almost every little chunk? Makes the video go by slowly when typing it could be much faster.
I now understand. Thank you kindly.
there is a callback in any delegate using begininvoke() which will also make the function run in different thread
never the less You did a great work thank you
Thanks!
Thank you for a very good and simple explanation
very good explanation, easy to understand - please make more videos
Good tutorial, but no need to F5 to check syntax. It is done automatically by Visual Studio as you type.
Agreed. Didn't say it right. F5 for me makes sure it runs. I like to stay running.
cool
Why the delegate needs to be public since it is not being called directly from outside of the class?
good tutorial, but I still don't see the advantage of this pattern, can you elaborate?
Imagine that you have Yes/No UI Window witch you wanna reuse in your app and buttons should do different things every time.So you can call your ShowWindow() function and as a parameters you can pass the addresses(functions) you want to be executed when Yes or No is clicked. Something like this: ShowWindow(OnYesCallback,OnNoCallback)
There is no difference in output with or without callback?
So what's really happening?
Is it just theory to understand that using delegate, our compiler will be doing other tasks rather than just waiting for a task to complete?
so what' s beauty of delegate based callback rather than calling function?
when you develop base program or DLL , It would be more flexible than just calling function.
where's my capital letters?
Why .net core?
.net core is popular for business and a lot of legacy systems use it.
And it does require a large install