Exercise 1: Install & Identify — Possible Solution ==================================================================== STEPS ------------------------------ 1. Download and install VS Code from code.visualstudio.com (or via a package manager, per the chapter's winget/brew/apt examples). 2. Launch VS Code. You'll land on the Welcome tab. 3. File -> Open Folder... and pick any folder on your machine (an existing project folder, or even just your Documents folder). WHAT TO LOOK FOR IN EACH REGION ------------------------------ Activity Bar (far-left icon strip): The topmost icon is the Explorer (usually already selected). Below it: Search (magnifying glass), Source Control (branch icon, with a small number badge if the folder is a git repo with uncommitted changes), Run & Debug (a play button with a bug), and Extensions (four squares). One specific thing to note: whether the Source Control icon shows a number badge — that alone tells you if the folder is a git repo with pending changes. Side Bar (next to the Activity Bar): With Explorer selected, this shows your open folder's file/folder tree. One specific thing to note: the folder name in bold at the top of the Side Bar — that's your currently open project's root. Editor Groups (the large central area): Empty at first (just the Welcome tab), or showing whichever file you've opened from the Explorer. One specific thing to note: the tab strip along the top of this area, showing every currently open file. Panel (bottom area, may be collapsed at first): Toggle it open via View -> Terminal (or Ctrl+`). One specific thing to note: the row of tabs inside it — Terminal, Problems, Output, Debug Console — all sharing this one region. Status Bar (thin strip at the very bottom): One specific thing to note: the current git branch name on the left (if the folder is a git repo), and the language mode / line number on the right, changing based on whichever file is currently focused in the Editor Group. WHY THIS WORKS AS AN ANSWER ------------------------------ Opening a FOLDER rather than a single file (per the chapter's own "Opening a Folder vs. a File" section) is what makes the Explorer, Source Control badge, and Status Bar's branch indicator all populate correctly — a loose single file wouldn't show any of that project- level context, which is exactly the distinction that section explains.