Installing Visual Studio and Setup

Analogy categoryAnalogies

Installing Visual Studio and Setting Up VB.NET

Visual Studio is Microsoft's full-featured IDE and the primary tool for writing, debugging, and running VB.NET applications; the free Community edition includes the same compiler, IntelliSense, and debugger as the paid Professional and Enterprise editions, making it the standard starting point for learning VB.NET without any licensing cost for students, open-source contributors, or individual developers.

🏏

Cricket analogy: It's like the BCCI providing the same DRS technology at a school-level exhibition match as at an IPL final — the free Visual Studio Community edition runs the identical VB.NET compiler and debugger as the paid Enterprise edition.

Downloading and Installing Visual Studio

Installation starts with the Visual Studio Installer, a separate bootstrapper downloaded from visualstudio.microsoft.com, which lets you pick which edition (Community, Professional, Enterprise) and which workloads to install rather than downloading one monolithic package; this modular approach means a VB.NET desktop developer's install can be a fraction of the size of a full ASP.NET and cloud tooling install.

🏏

Cricket analogy: It's like a cricket kit shop letting you buy just the batting pads and gloves you need instead of an entire pre-packed kit bag, similar to the Visual Studio Installer letting you select only the workloads you need rather than one giant download.

Selecting the .NET Desktop Development Workload

To write VB.NET console or Windows Forms applications you must check the '.NET desktop development' workload in the installer, which bundles the VB.NET and C# compilers, the .NET SDK, NuGet package manager, and the Windows Forms and WPF designers; skipping this workload means the 'Console App' and 'Windows Forms App' VB.NET project templates simply won't appear when you try to create a new project.

🏏

Cricket analogy: It's like a team needing the full fielding-drills kit, not just bats, before a coach will let them practice slip catching — without the .NET desktop workload, the Console App and Windows Forms templates simply won't show up in Visual Studio's new-project list.

Creating Your First VB.NET Project

Once installed, you create a new project through File > New > Project, filter the template list by language 'Visual Basic,' and choose a template like 'Console App'; Visual Studio then scaffolds a .vbproj file, a Program.vb (or Module1.vb) file with a Sub Main entry point, and restores any NuGet dependencies automatically before you can hit F5 to build and run.

🏏

Cricket analogy: It's like a captain filling out the official team sheet before the umpire allows play to start — filtering by 'Visual Basic' and picking Console App scaffolds the .vbproj and Program.vb before you can press F5 and 'take strike.'

vbnet

Module Module1
    Sub Main()
        Console.WriteLine("Setup complete!")
    End Sub
End Module

If you install Visual Studio without the .NET desktop development workload, you can add it later via Tools > Get Tools and Features rather than reinstalling — but forgetting this step is the most common reason beginners can't find the VB.NET project templates.

Visual Studio Community edition is free and includes the same VB.NET compiler and debugger as paid editions.
The Visual Studio Installer lets you select modular workloads instead of one giant download.
The .NET desktop development workload is required to see VB.NET Console App and Windows Forms templates.
Creating a new project scaffolds a .vbproj file and a Program.vb or Module1.vb with a Sub Main entry point.
You can add missing workloads later via Tools > Get Tools and Features without reinstalling Visual Studio.
F5 builds and runs your VB.NET project with the debugger attached.