Visual Studio 97: five languages, one box
Microsoft shipped Visual Basic and Visual C++ as entirely separate products until 1997. If you wanted both — and 60 percent of Visual C++ developers did — you bought two boxes, installed two programs, and accepted two different user interfaces. Doug Hodges, who would become one of the IDE architects at Microsoft, later described the situation plainly: “We had a separate IDE for VB at that time, then we had VC, VJ, and VI in this dev shell.” The only thing linking them was the shelf.
On March 19, 1997, Microsoft shipped a single product called Visual Studio 97 — codenamed Boston, inaugurating what became a long tradition of naming releases after cities — and put five complete development environments inside. Visual Basic 5.0 for Windows application development. Visual C++ 5.0 for systems and performance work. Visual J++ 1.1 for Java. Visual InterDev 1.0 for building dynamic web sites with Active Server Pages. Visual FoxPro 5.0 for databases. Plus the MSDN Library documentation disc. Professional edition shipped on three CDs; Enterprise on four.
The decision to bundle was driven by arithmetic. Microsoft’s own data showed that over half of professional developers were using more than one language, with 90 percent of Java developers reaching for at least one other tool. Bob Muglia, Microsoft’s VP of developer tools, framed the product at launch as “the first comprehensive set of tools that enables customers to combine rapid advances in client/server technologies with the broad reach of the Internet.” Internally, the concept was blunter: Visual Studio was conceived as “Microsoft Office for developers.”
Julia Liuson, who joined the Visual InterDev team in early 1996, described her piece of the bundle as “Visual Basic for the web.” She would eventually lead Microsoft’s entire developer division. At the time, her goal was narrower: make web development feel as approachable as building a Windows form. Visual InterDev was the newest and most speculative component — Active Server Pages had only just shipped — and its inclusion in the box committed Microsoft to the web as a first-class development target rather than an afterthought.
Visual Studio 97 bundled the tools without fully unifying them. Each language still ran its own IDE underneath; the box was the integration, not the shell. The real architectural work — a single host process that could load any language’s toolchain interchangeably — took until Visual Studio .NET in 2002. By then, Visual J++ was gone, eliminated after Sun Microsystems sued Microsoft for shipping a Java implementation that didn’t comply with Sun’s specifications. From that legal wreckage came C# and the .NET runtime. The death of one language seeded an entire platform.
What March 1997 established was a premise: your development environment is a platform, not a collection of programs. The version numbers across the bundle were synchronized in Visual Studio 6.0 the following year — Visual Basic 6.0, Visual C++ 6.0 — because the suite had become the product. Every IDE that followed, from Eclipse’s plugin architecture to VS Code’s extension marketplace, inherits that argument.
Sources
- Microsoft Announces Visual Studio 97 — Microsoft Source — original announcement with developer usage statistics and Bob Muglia quote on client/server and web convergence
- Visual Studio — Wikipedia — codename Boston, March 19 1997 release date, edition structure, and the transition to Visual Studio .NET
- History of the VS IDE — Code Magazine — Doug Hodges on the fragmented pre-VS architecture and the COM-based unification strategy
- The Faces Behind Microsoft Visual Studio — Thurrott.com — Julia Liuson on Visual InterDev and the “Microsoft Office for developers” concept