Microsoft says it is working on Visual Studio Live Share, letting developers collaborate on the same codebase without the need to synchronize code
We are excited to announce that we're working on “Visual Studio Live Share”, which enables developers using Visual Studio 2017 or Visual Studio Code to collaborate in real-time!
Context & Ripple Effects
The announcement lands between two milestones in Microsoft's editor strategy: the open-sourcing of Visual Studio Code in 2015 and the general availability of Visual Studio 2017 earlier that year, which pushed multi-platform development and a more modular IDE. Live Share extends that trajectory from open tooling to shared sessions — collaboration built into the editor rather than bolted on through version control.
First-order effects
- Developers on Visual Studio 2017 and Visual Studio Code gain real-time co-editing and debugging on a single codebase, removing the clone-branch-sync ritual that pair programming currently requires.
- Microsoft turns its two editors into collaboration endpoints, making session-sharing a differentiator for the installed base it already has across Windows, Mac, and Linux.
Second-order effects
- Collaboration-as-a-feature pressures rival editors and cloud IDE vendors to match shared-session capability natively, shifting competition from language support toward the editing experience itself.
- Hosting live sessions requires Microsoft to run the relay infrastructure, pulling the company further into operating developer services — groundwork visible later in Visual Studio Online, the browser-based editor it previewed in 2019 and opened to public preview that November.
Third-order effects
- If the pattern holds, the IDE stops being a local application and becomes a hosted workspace where presence, sharing, and compute live server-side — the structural shift Visual Studio Online made explicit two years later.
The trend: Developer tools are moving from locally installed editors to cloud-hosted collaborative workspaces, with Microsoft using Live Share as the bridge between its desktop IDEs and that hosted future.