Mono Tools and the Teamprise Acquisition Extend Visual Studio's Appeal -- Visual Studio Magazine

By Andrew J. Brust

Visual Studio's Cross-Platform Play

I like it when Microsoft bridges its technologies to other platforms. I like the PHP Driver for SQL Server and the samples in the PHP On Windows Training Kit so much that I did a whole session on them at VSLive! last month. The ADO.NET Data Services (Astoria) bridges for PHP and Java are very exciting to me. The Silverlight plug-in for Eclipse, the Azure SDK for Java, and the Windows 7 support for Eclipse are all good stuff.

To add to these recent developments, Microsoft has announced its acquisition of the Teamprise products from SourceGear. These are non-.NET, Team Foundation Server clients in the form of an Eclipse plug-in, a stand-alone client and a command line client, suitable for scripting. The clients work on Windows, Mac OS X, Linux and Solaris.

And beyond this Microsoft announcement, Novell announced its Mono Tools plug-in for Visual Studio, allowing .NET developers to target non-Windows platforms, without leaving the comfort of Visual Studio IDE and their favorite add-ins for that IDE.

With these products and technologies, Microsoft does both well and good. They build good will, they add credibility to their products and they diversify the customer base. I suppose a more skeptical view is that these products and initiatives erode the strength of Windows in the marketplace. But I don’t buy that. From what I can tell, Windows has the power to erode its own position (as Vista did) or strengthen it (as Windows 7 seems to be doing), all by itself.

I liken the Teamprise and Mono Tools’ widening of the Visual Studio customer base to the similar cross-platform adoption of Exchange facilitated by the licensing of ActiveSync. The latter has made Exchange a platform supported by iPhone, Android and Palm’s WebOS devices, in addition to its long-standing support on Blackberry and Windows Mobile. Given the strength of the newer smartphone platforms, (and the increasing weakness of Windows Mobile), this cross-platform support turns out to be really important for the continued strength of Exchange. Likewise, support on other operating systems for TFS and new support for other operating systems in the Visual Studio IDE help establish Microsoft development and ALM tools as true standards, rather than simply incumbents for the Windows platform.

I don’t know if everyone in Redmond is happy about these developments, but they should be, because this interoperability gives Microsoft gravitas, and a better-assured franchise than it would otherwise have.

Posted by Andrew J. Brust on 11/13/2009

comments powered by Disqus

Featured

VS Code 1.130 Expands Agent Host and Review Tools

Microsoft's latest weekly VS Code release advances shared agent sessions, multi-file change review, chat visibility and terminal navigation
Microsoft Agent Framework Makeover: Claws, Loops and Harnesses

Microsoft's newly released Agent Framework Harness packages the loops, planning, memory, context management and safety controls that developers previously had to assemble around AI models themselves.
Visual Studio 2026 Gives Copilot Built-In Skills -- and Makes Them Prove Their Worth

Microsoft is moving Agent Skills beyond bring-your-own instructions by shipping expert-authored workflows with the IDE, while keeping them off by default until testing shows their benefits justify the additional token use.
Copilot AI Billing Shock Met with Meters, Caps and Token-Saving Tools

GitHub is layering spending limits, expanded credit allowances and increasingly granular usage reporting onto Copilot, while Microsoft is reworking Visual Studio and VS Code to expose -- and reduce -- the cost of agentic development.