Welcome back.
In this video, I want to give you a quick overview over the most important parts of Visual Studio of
the user interface.
So all of the things that you see on the screen right now.
So what you can see is obviously we have here all of the options that are made available for us, all
of the things that we can do inside of Visual Studio.
But what's more important or relevant is these parts here where you see our program CSS file, which
is our file in which we currently have all of our code.
Later on, we're going to create more of these files that will contain our code.
But for now we're going to keep it really simple and have it all in here.
So this we saw this is where all of our code goes into.
So this whole portion right here at the bottom you see that we get the output.
So here we can read what kind of output we get from our debugger.
So basically it helps us to later on find errors that we have in our code and so forth.
So for example, if I don't have a semicolon here and I try to run it, I get an error.
It says it could not run successfully.
And well, Visual Studio basically already tells me it can't run it.
And at the same time, here at the bottom, I get this error list where it says it expected a semicolon
in line six, which is this line here.
And luckily enough, Visual Studio even tells us here that it expected a semicolon.
So we can just add that back in.
So here at the bottom, by default you see your error list and you see the output.
So you can select the window that you are interested in.
You can have more windows in here as well by going to view and add more in here you can see there are
a bunch more, but it's not something that should overwhelm us at this point.
We don't need any of that.
You can see there are plenty of other windows that we can add later on, but for now, what's important
is really this error list, and the output and the error list is displayed to us automatically.
Once we do have an error or a warning in our application, which is pretty useful.
And then on the right hand side you see your solution explorer, which has all of the files that you
have inside of your project.
So if you look at our program.cs file, you can see that it's this file here.
And let me actually save my project by clicking on this button or by pressing Ctrl S on windows.
On Mac it's command S.
And then let's right click onto our program CS and then open this file or open containing folder here
this one.
And you will see that on our PC we now have all of these files.
So inside of our Hello World two folder I'm moving over to that.
You can see that we have our Hello World Visual Studio solution file.
That's this SLN extension.
And then this basically opens up our project.
So if I click on that it will open the Visual Studio project that we have built, which is again going
to be the same that we've used so far.
It's just going full screen.
I have this white screen monitor here, but basically just opens up the project again.
Now the cool thing is if you open this folder hello world two, you can see that this is where our program
CSS file is and you can open it.
Let's say you want to open it with the editor.
You will see that this is the code that is inside of our program CSS file.
So here you can see we have this program CSS file plus our C sharp project file.
So Csproj you can open it with Visual Studio 2022 as well, which will then also open up your project.
And there you are.
And on top of that we have an objects folder as well as a bin folder which contains the debugging of
the.
Net eight.
So that's just the structure of the project.
And whenever we create a new folder or a new file in here, it will be displayed here on the solution
explorer as well.
Now let's look at the most important buttons that we have here at the top.
So we have this Hello World button which basically is the project name that we have.
And this play button here we can select to run it.
We can debug properties.
We're going to see what debugging is later on.
And then there is this other button next to it which is also a play button.
But it's not filled.
And it allows me to start without debugging, which means I don't get debugging information here at
the bottom.
What is debugging?
Even debugging is basically you want to eliminate bugs by debugging.
So what is a bug?
A bug is an error in your code, so it's not the end or uh, any other kind of bug.
It's an actual error in your code and sometimes the errors are visible.
Like for example, this one is very easily visible.
This is an error that we can see as our Visual Studio is compiling.
But then there are errors which occur only during runtime.
Which basically means once the program is executed.
So once you actually run the app or the program that you wrote, then once you get an error in that
case, that's called the runtime error.
And if you do our debugging, then you can catch the error and make sure that your program doesn't crash.
And you can try to fix the error this way.
But we're going to cover debugging in more depth later on into the course.
But for now, I just wanted to give you an overview of these few things, and also give you a little
bit of a background information regarding those different parts of our approach here.
Okay.
So that's it for this video.
See you in the next one.