News

Microsoft Promotes Tools for Silverlight on Mac

Microsoft's attempts to plug in to cross-platform got more convincing last week when development on the Macintosh became a reality with Silverlight 3.

The company has partnered with Paris-based software developers Soyatec to deliver an Eclipse4SL plug-in for the Mac. The technology preview of Eclipse4SL for Mac, available now, follows Eclipse4SL for Windows, announced last October in conjunction with Silverlight 2 and released in January under the Eclipse Public License 1.0.

The open source project, which works with the Eclipse IDE and RCP, has been submitted to the Eclipse Foundation. Soyatec is an Eclipse Foundation member, and created eFace, a XAML/WPF editor for Java developers.
 
The Windows and Mac plug-ins will offer comparable feature sets, according to Vijay Rajagopalan, the principal architect on the Microsoft Interoperability Strategy team who is heading the project in Redmond. Rajagopalan joined Yves Yang of Soyatec to host a session on Eclipse4SL at this week's EclipseCon in Santa Clara, Calif.

The project developers are working on adding debugging capabilities and collocation support to Eclipse4SL in the summer timeframe, Rajagopalan said. Version 1 of the Mac plug-in is expected around August.

"[J]ava developers use middleware for enterprise applications. When it comes to RIA, they typically use PHP or other tools," Rajagopalan said. "They don't necessarily use Java. And we thought, why don't we enable rich Internet applications for Java developers? What is the best means of accomplishing that? And Eclipse is their platform."

Rajagopalan also pointed to feedback from Silverlight customers about the interoperability issues between the cross-browser plug-in and Java Web Services that use SOAP, REST and JSON. "We thought this project will not only solve the RIA challenge but also solve the interop challenge that exists between Java applications and Silverlight," he said.
 
Eclipse4SL provides a project system, a C# and XAML editor and preview, and a compiler for packaging Silverlight applications. The Eclipse-based SDLT uses a similar structure to the project system in Visual Studio. XAML and Silverlight applications can use Eclipse or Visual Studio project resources. The apps will also be supported in Expression Blend, according to Microsoft.

At MIX 09, Microsoft also announced support for Adobe Illustrator and Adobe Photoshop files in Expression Blend 3, made available as a technology preview last week.

"[O]ne of the things we're doing is enabling designers using Macs to be able to create assets that we can then import within Blend, and use to build great Silverlight applications," said Microsoft Corporate Vice President Scott Guthrie during the keynote.

Developers will also be able to build Silverlight 3 applications that run outside of the browser, on both Windows and the Mac, according to Guthrie.

About the Author

Kathleen Richards is the editor of RedDevNews.com and executive editor of Visual Studio Magazine.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube