Skip to main content

Xamarin 2.0: bringing cross-platform development to the next level

Xamarin brought cross-platform mobile development to the next level. With the announcement of Xamarin 2.0 comes a rebranding of their products, a new IDE called Xamarin Studio, a Visual Studio add-in for iOS development, and the introduction of a component store.

Xamarin Studio

Xamarin Studio is the successor of MonoDevelop. It has a new interface and provides some of the functionality familiar to Visual Studio developers: auto-completion, refactoring, syntax highlighting, code tooltips, code navigation, integrated debugger for simulator/emulator or the real device, integration with Git and Subversion. Don’t forget to have a look at ‘the making of’.

Visual Studio Add-in for iOS development

Xamarin offered the option to do iOS development before, but you couldn’t use Visual Studio and had to switch to MonoDevelop(which was a great IDE by the way). Now Xamarin fixed this by releasing a Visual Studio add-in for iOS development. This add-in offers good integration with Microsoft’s ecosystem including remote debugging and testing in a simulator on a Mac OS machine(so you still need a Mac OS machine to test your application).

Component Store

The last new feature that Xamarin 2.0 introduces is the Component Store. Xamarin has built a framework for creating, sharing and reusing components directly from the IDE increasing the development speed.The store offers ready-to-use mobile themes, Xamarin.Mobile providing an API for accessing common platform features, and much more…

Have a look at http://components.xamarin.com/.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...