If I've seen a Block Level var, I didn't know it's scope or how it worked till this vid. I didn't know how Form1_Closing worked and I had never heard of Closed. WOW . I stop the vid and take notes each time I learn something new. Thank you so much for being you and what you do for us out here....JT
Thank you so much for sharing these lessons. I am taking a beginning VB course online through a college this semester and it has been a nightmare. The instructor has been a complete ghost. The textbook introduces too many new concepts in each chapter and doesn't give enough short targeted practice. The tutorials are pages of code long and involve so many other concepts that it's overwhelming. I was almost ready to give up when I found this series on UA-cam. It has been a lifesaver. I'm actually enjoying programming again. I will send you some $ Love as soon as I'm able. Thank you again. I hope you continue creating these videos!
Loving these videos. I'm trying to get back into programming after 15 years. In those 15 years, I've just dabbled in VBA here and there so it is fun learning the new system. Also, glad to see loads of similarities with VB6. I think database access may be the biggest change so I am looking forward to seeing that video. Also, I remember dabbling in object arrays a bit in VB6 so I'm not sure how that works in VB.NET yet.
Hey man, first of all, found your videos today, great stuff, real simple to listen/understand (if the brain can comprehend the advanced level of coding required sometimes xD) Quick question, how did you get that toolbar for quick defining events under the Form Explorer Btw, do you do any personal lessons? Thanks
I see you welcome the user in Form1, but I tried to do it in Logon form and it worked too. But when I defined two welcome strings, one in Form1 and one in Logon, only the latter appeared. Any idea why?
You need to define the welcome string somewhere that both forms can see it. That means in a module with the public keyword. Add a module to the project and put the following code in it: Public stWelcome As String = "hello world" The welcome string should be available to both forms. (There are other ways to do this, but they require some knowledge of OOP, which I've covered in another series) :)KD
It's not a bad idea, but it would depend on the size of the application and how many people were working on it. I have worked for software companies that do exactly what you suggest. Others might group variables according to purpose. Ultimately, it's about making your particular application easy to maintain. :)KD
Form1. Show... Form1 is a Class, its a bit silly that this works for forms. But usually you would .Show an Instance of the class Form1 Little joke for this one, try: Form1 = Nothing; Form1. Show This makes absolutely no sense for any other class then forms, because forms get automatically created instances, which confuses beginners once they try to to anything more advanced with forms.
Forms (and the classes they reference) are indeed a special case, most classes don't affect the user interface. You can of course create multiple instances of the same form. Perhaps I will dig into this in an Advanced course. :)KD
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
If I've seen a Block Level var, I didn't know it's scope or how it worked till this vid. I didn't know how Form1_Closing worked and I had never heard of Closed. WOW . I stop the vid and take notes each time I learn something new. Thank you so much for being you and what you do for us out here....JT
Thank you for watching. It's a pleasure to be of service :)KD
Thank you so much for sharing these lessons. I am taking a beginning VB course online through a college this semester and it has been a nightmare. The instructor has been a complete ghost. The textbook introduces too many new concepts in each chapter and doesn't give enough short targeted practice. The tutorials are pages of code long and involve so many other concepts that it's overwhelming. I was almost ready to give up when I found this series on UA-cam. It has been a lifesaver. I'm actually enjoying programming again. I will send you some $ Love as soon as I'm able. Thank you again. I hope you continue creating these videos!
Thank you for this! can't wait for the next video!
thank u very much, sir I follow your channel, and I get so much knowledge thank you, sir.😊
You are very welcome :)KD
Loving these videos. I'm trying to get back into programming after 15 years. In those 15 years, I've just dabbled in VBA here and there so it is fun learning the new system. Also, glad to see loads of similarities with VB6. I think database access may be the biggest change so I am looking forward to seeing that video. Also, I remember dabbling in object arrays a bit in VB6 so I'm not sure how that works in VB.NET yet.
Finally! Thank you for the lesson.
More on the way as soon as the work load lightens. We teachers are doing the exam boards' job for them these days.
Hey man, first of all, found your videos today, great stuff, real simple to listen/understand (if the brain can comprehend the advanced level of coding required sometimes xD)
Quick question, how did you get that toolbar for quick defining events under the Form Explorer
Btw, do you do any personal lessons? Thanks
very good explanation of variable scope.
Excuse my ignorance, but I missed a step here. How did you end up with 2 Form2s (~8:15)?
See ua-cam.com/video/IiWKnRSEwMY/v-deo.html
:)KD
Your videos are incredible good. I love everything about them
Thank you :)KD
Good to have the second part men ❤️
First view!!! - Part 3 is on the way this week (I hope) :)KD
@@ComputerScienceLessons I needed this tutorials a year ago, damn they would be useful as hell ❤️😉thanks men , 101% sub
I see you welcome the user in Form1, but I tried to do it in Logon form and it worked too. But when I defined two welcome strings, one in Form1 and one in Logon, only the latter appeared. Any idea why?
You need to define the welcome string somewhere that both forms can see it. That means in a module with the public keyword. Add a module to the project and put the following code in it:
Public stWelcome As String = "hello world"
The welcome string should be available to both forms.
(There are other ways to do this, but they require some knowledge of OOP, which I've covered in another series) :)KD
@@ComputerScienceLessons is it a good practice in general to put all public variables in a module and call it "public variables module?"
It's not a bad idea, but it would depend on the size of the application and how many people were working on it. I have worked for software companies that do exactly what you suggest. Others might group variables according to purpose. Ultimately, it's about making your particular application easy to maintain. :)KD
that is so cool
Form1. Show... Form1 is a Class, its a bit silly that this works for forms. But usually you would .Show an Instance of the class Form1
Little joke for this one, try: Form1 = Nothing; Form1. Show
This makes absolutely no sense for any other class then forms, because forms get automatically created instances, which confuses beginners once they try to to anything more advanced with forms.
Forms (and the classes they reference) are indeed a special case, most classes don't affect the user interface. You can of course create multiple instances of the same form. Perhaps I will dig into this in an Advanced course. :)KD