Microsoft woos open sourcers with Visual Studio 2010
What price MySQL?
Licensing could prove to be a sticking point, particularly in the case of open-source components for Visual Studio. Microsoft decided early on that it can't ship external open-source code with Visual Studio that uses a license that could expose it to IP litigation down the line.
This limitation could be navigated, however, should projects come with a license that's considered business-friendly - JQuery, for example, is under MIT in addition to GPLv2. Alternatively, code could be downloaded for use with Visual Studio instead of being shipped by Microsoft with the IDE, a step that would protect Microsoft from legal blow-back in any potential IP action.
A harder problem for Microsoft would be to persuade members of the open-source community to want to help, given the history of competition and animosity between them and Redmond.
Zander said Microsoft has tried to work closely with the open source community to prove its good intentions. He listed as positive moves the inclusion of the OSI-license compatible Dynamic Language Runtime in Visual Studio, allowing its IronRuby to be hosted on Ruby Forge, along with its willingness to take feedback on the scripting language and the fact Python author Jim Hugunin works on Zander's team on IronPython.
"We also know that to be a first-class member of that community - Ruby and Python are an example - it requires for us to work in that kind of way," Zander said.
The appeal to open-source comes as Microsoft takes steps to make it easier for the 200 partners in the official Visual Studio Industry Program (VSIP) to build plug-ins for Visual Studio 2010. This will be the first version of Microsoft's IDE with the shell written in its Windows Presentation Foundation (WPF) graphical subsystem, which separates the interface from the business logic.
According to Zander, WPF will let partners write plug-ins without focussing overly on the interface, since WPF will take care of that. He already expects partners to take the Visual Studio SDK and build components.
"[Partners] can spend more time figuring out what the data has to hook up to and less of their time writing really low-level graphics code," Zander said. ®