Intro to Visual Studio TODO intro

[daniefer]

We have lots of different short cuts and tools to do our everyday jobs when in Visual Studio (VS for short). There is a lot in VS I don't know because I don't need to know. As you develop your coding skills you will see what you need to know and don't. To start with though, explore the `File` menu and `Edit` menu. From `File` you can open and close project, create new ones, and open recent projects/solutions. Edit lets you do all sorts of stuff text manipulation: Find/Replace, Copy line, sort lines, make uppercase/lowercase, comment, indent, etc. Some of my favorite VS shortcuts are:

* Copy/Cut/Paste a whole row
* Move a line of code up or down
* Auto format document on save
* Sort and remove unused using statements
* Go To ...

All menus are context aware. That means, depending on where you last clicked tabbed off of, etc the menu options change. For example, close all files then open the `Edit` menu. Different stuff is in there. 

Lastly, everything in all the menus can be configured to a hot key. Checkout `Tools` > `Options` for everything you can possibly configure. Visual Studio can be reset to "factory settings" so I would not worry too much about what you change. Factory reset is pretty easy. If you mess something up (or think you did), just go to `Tools` > `Import and Export Settings...` and select `Reset all settings`. When you get to the `Choose your Default Collection of Settings` screen, pick `Visual C#`.

[daniefer]

More notes:

> #### Note::Solutions vs Projects
> 
> Up to this point, you have have likely only been working in Visual Studio Code (_VS Code_ or _Code_ for short). VS Code opens a directory and you just work with the files in it. You likely only had one project and possibly only one file to work with. Web applications take a bit more than that. In this class we will work with 10s-100s of files, depending on how large your final project turns out. 100 files is a lot. So to better organize and contain our code both in class and in the "real world", we split our application's code into multiple projects. This let's put boundaries on what is and is not part of a "domain"/area of concern for a particular class/file/concept. We then need a way to bring those projects together to work as one application. We specify which projects need to work together in a file called a solution. So to recap: classes are in files, files are in projects, projects in solutions. We will start almost every class by opening a new or existing solution (.sln file). When you open a project (.csproj file) in VS, you will likely get prompted to save the "solution" when you close. This is because VS adds all projects it opens to a solution if you did not open a solution. Keep this in mind when opening and closing VS and try not to freak out about popups. Remember: breath and read, then click. 😁

For more in depth into to VS, checkout the [Visual Studio IDE getting started](https://docs.microsoft.com/en-us/visualstudio/get-started/visual-studio-ide?view=vs-2017) guide.