VS Code Setup And Course Extensions

Objectives

• Open the repository root as the VS Code workspace
• Use a course profile to keep extensions and settings organized
• Run course commands from the integrated terminal
• Install only the extensions established for the enrolled course

Install And Open VS Code

• Download the desktop application from code.visualstudio.com if it is not already installed
• Install VS Code outside the course repository folder
• Open VS Code Desktop; browser-based VS Code does not provide every local extension, runtime, or terminal capability

Open The Repository Root

• Open the folder where git status succeeds, not a nested module or one individual file
• Select File -> Open Folder, choose the repository root, then select Trust only when it is a repository you cloned or created
• You can also run code . from the repository root
• VS Code Explorer should show the repository files and Source Control should show the repository branch

Create A Course Profile

1. Open the Manage gear in the lower-left corner, then select Profiles
2. Select New Profile
3. Name the profile for the course or technology stack, such as IT202, IT114, PHP, or Java
4. Choose Empty Profile for a clean course setup, then select Create
5. Install the course extensions only after that profile is active

A profile keeps course extensions and settings separate from unrelated projects

Confirm The Active Profile

• Open Manage -> Profiles to see the active profile
• The active profile can also appear as a label or icon on the Manage button
• The selected profile is associated with the repository folder currently open in VS Code
• Use Profiles: Switch Profile from the Command Palette to change profiles later
• An extension improves editor feedback or workflow; it does not replace course commands, testing, or review
• Do not store passwords, private keys, or other secrets in tracked workspace settings

Set The Integrated Terminal

1. Open Terminal -> Select Default Profile or use the dropdown beside the new terminal button
2. On Windows, choose Git Bash
3. On macOS and Linux, keep the detected built-in terminal unless the setup instructions say otherwise
4. Select Terminal -> New Terminal to open a terminal inside VS Code

This changes the terminal used inside VS Code, not the system-wide default terminal

Verify The Terminal And Workspace

• pwd should show the repository root
• git status should report the current branch or a clean working tree
• Commands behave the same as they do in another local terminal
• The editor, terminal, runtime, and remote environment are separate tools; an extension does not install every dependency

Choose The Course Extension Set

Install required extensions in the active VS Code profile. Recommended extensions are helpful but are not a grading requirement.

Use the vertical course slides as the current shared reference. A course setup page may add a tool later when a unit needs it.

IT202: Internet Applications

Required

• GitLens (GitKraken) for in-editor Git history, blame, and branch visibility
• PHP Intelephense for PHP language support, syntax checks, and warnings
• WakaTime for the activity evidence required with homework submissions

Required Before Database Work

• MySQL (cweijan) to connect to and inspect the course database

Recommended

• Auto Rename Tag for matching HTML tags while editing
• Bracket Lens for matching and closing-bracket cues
• Todo Tree for finding TODO and FIXME comments

Host PHP is optional; later VM and hosted paths can run PHP. Keep database credentials out of tracked files.

IT114: Java Advanced Programming

Required

• Extension Pack for Java (Microsoft) for Java language support, debugging, and tests
• GitLens for in-editor Git history and branch visibility
• WakaTime for the activity evidence required with homework submissions

Recommended

• Bracket Lens for matching and closing-bracket cues
• Todo Tree for finding TODO and FIXME comments

Compile and run through the command-line course workflow even when VS Code offers a launch button. Browser-based VS Code does not supply every local extension or runtime capability.

IT490: Systems Integration

Required

• No course-specific VS Code extension is prescribed
• Use the repository root workspace and the editor or remote tools named by each current setup or milestone instruction

Recommended

• Add an extension only when it supports the assigned system or team workflow
• Do not assume a local extension replaces validation on the assigned systems

IT265: Game Architecture And Design

Required

• No course-specific VS Code extension is prescribed
• Use the repository root workspace and the tools required by the selected project technology

Recommended

• Add tools only when the current IT265 instructions recommend them
• Keep design files, notes, and project assets organized within the course repository

Set Up The IT202 MySQL Extension

1. In the active IT202 profile, open Extensions, search for MySQL, and install MySQL (cweijan)
2. Open the MySQL panel in the VS Code sidebar and create a new connection
3. Get the generated DB_URL from courses.ethereallab.app/database
4. Enter its separate values in the connection form:
   • Host: db.ethereallab.app
   • Port: 3306
   • Username and database: your UCID
   • Password: the generated database password from the course database page
5. Save the connection for later database lessons

The extension is for IT202 database inspection and query practice. Do not commit the connection password or place it in tracked VS Code settings.

Set Up WakaTime For IT202 And IT114

WakaTime is required for activity evidence submitted with IT202 and IT114 homework. It uses your own WakaTime account and API key.

1. Create or open an account at wakatime.com/signup
2. Copy the API key from the WakaTime account settings
3. In the active IT202 or IT114 profile, install the WakaTime extension
4. Open the Command Palette with Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS
5. Run WakaTime: API Key, then paste the key
6. Open and edit a repository file; restart VS Code if activity does not appear

Keep the API key private. WakaTime activity complements Git history; it does not replace commits or homework evidence.

Common Troubleshooting

Knowledge Check

Key Terms And Further Learning

• Workspace root: The opened repository folder where git status succeeds.
• Profile: A named set of VS Code settings and extensions for a course or task.
• Integrated terminal: A shell opened inside VS Code at the current workspace.

Further Learning:

• VS Code profiles
• VS Code terminal profiles

Summary

• The repository root is the folder whose name matches the repository and where git status succeeds
• A VS Code profile keeps each course or technology stack's extensions and settings together
• On Windows, use Git Bash in the integrated terminal and verify the workspace with pwd and git status
• Course extension lists distinguish required tools from helpful recommendations
• IT202 uses the course database connection from the course database page; IT202 and IT114 use WakaTime for homework activity evidence
• Extensions support the course workflow but do not replace commands, testing, Git history, or required evidence

Next presentation: TRACE Learning Journal Foundations