News

Xamarin 3 Unveiled

Tighter integration with Visual Studio among the highlights.

Xamarin, which makes it possible for developers to use C# to build applications for iOS and Android devices, is making news on several fronts today, with an acquisition and release of a new edition of its flagship product.

The bigger news is the announcement by Xamarin co-founder Nat Friedman of the release of Xamarin 3. Most of the upgrades revolve around tighter integration with Visual Studio. Friedman lists upgrades in four main areas:

  • Xamarin Designer for iOS. The designer uses the iOS Storyboard format that will be familiar to iOS developers. It's fully integrated with Xamarin Studio, the standalone IDE, and Visual Studio. Xamarin Studio also has a Mac-specific version.
  • Xamarin.Forms. This is a UI builder available as a portable class library (PCL). Xamarin.Forms pages "represent single screens within an app," Xamarin says. Connecting common controls like lists, labels and buttons to the shared C# backend code means that a developer could create a page that will display the same across a Windows Phone, iPhone and Android phone.
  • IDE Upgrades. This is where a lot of the Visual Studio integration happens. Xamarin says it has combined its iOS and Android extensions into a single Visual Studio extension; added full support for NuGet packages; published complete documentation for the .NET Base Class Libraries (for which they thank Microsoft) into Xamarin Studio; and added support for the growing F# language.
  • Code Sharing. Xamarin 3 allows developers to use Shared Projects. They enable code sharing between multiple target projects, including Xamarin applications. "They support compiler directives so that you can conditionally include platform-specific code to be compiled into a subset of the projects that are referencing the Shared Project," according to Xamarin. Shared Projects was originally a part of Visual Studio 2013 Update 2, released May 12.

Xamarin has four versions, beginning with a free Starter edition, up to $1,899/year, per platform, per developer for the Enterprise edition. Xamarin 2.0 was released Feb. 20, 2013.

The other announcement Friedman made was the acquisition of the Visual Studio Extensibility (VSX) Division of Clarius Consulting. Friedman called Clarius "...the world's foremost experts on extending Visual Studio." Some of its extensions include Visual T4, IronPython Studio, Default Browser Switcher and Debugger Canvas.

A page on the Clarius Web site said that the sale of VSX will allow the company to focus on other areas like mobile, cloud and embedded computing. Microsoft is a major Clarius customer, perhaps fueling speculation that Microsoft may still be considering an acquisition of Xamarin. As ZDNet and Redmond Magazine columnist Mary Jo Foley reports, though, there's been no movement on that front lately. The terms of the purchase were not announced.

About the Author

Keith Ward is the editor in chief of Virtualization & Cloud Review. Follow him on Twitter @VirtReviewKeith.

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