Normally, I wouldn't open a second solution, but this is nothing to do with the original question ...
Quote:
I try to use String.Contains() like this but when i start to compile the program it show the message error
System.NullReferenceException: Object reference not set to an instance of an object.
at WindowsApp1.Form1.Form1_Load(Object sender, EventArgs e) in C:\Users\USER\source\repos\WindowsApp1\WindowsApp1\Form1.vb:line 20
No, it isn't. That isn't a compiler error, that's a runtime error. They are very different beasties. You only get compiler errors before you code runs, you get runtime errors after tha. Unless your code compiles without errors, it cannot run!
And the compiler can't spot runtime errors - they even have a different name: they are
exceptions.
So ... let's look at a null reference exception, and why it happens, because this is one of the most common problems we get asked, and it's also the one we are least equipped to answer, but you are most equipped to answer yourself.
Let me just explain what the error means: You have tried to use a variable, property, or a method return value but it contains null - which means that there is no instance of a class in the variable.
It's a bit like a pocket: you have a pocket in your shirt, which you use to hold a pen. If you reach into the pocket and find there isn't a pen there, you can't sign your name on a piece of paper - and you will get very funny looks if you try! The empty pocket is giving you a null value (no pen here!) so you can't do anything that you would normally do once you retrieved your pen. Why is it empty? That's the question - it may be that you forgot to pick up your pen when you left the house this morning, or possibly you left the pen in the pocket of yesterday's shirt when you took it off last night.
We can't tell, because we weren't there, and even more importantly, we can't even see your shirt, much less what is in the pocket!
Back to computers, and you have done the same thing, somehow - and we can't see your code, much less run it and find out what contains null when it shouldn't.
But you can - and Visual Studio will help you here. Run your program in the debugger and when it fails, VS will show you the line it found the problem on. You can then start looking at the various parts of it to see what value is null and start looking back through your code to find out why. So put a breakpoint at the beginning of the method containing the error line, and run your program from the start again. This time, VS will stop before the error, and let you examine what is going on by stepping through the code looking at your values.
But we can't do that - we don't have your code, we don't know how to use it if we did have it, we don't have your data. So try it - and see how much information you can find out!