Contents tagged with Xamarin.Android
The following is a link to cross platform data access training with Xamarin & C#. It is intended for use on iPhone, iPad, and Android devices. The course covers local data in Sqlite, calling Web Services via REST and JSON, and calling Sql Server.
My training on Cross Platform Development with Xamarin w/ Portable Class Libraries and ASP.NET Razor Templating is now available online from Learn Now Online. The url is: http://www.learnnowonline.com/course/cpx1/xamarin-cross-platform-pcl-and-razor
Authentication has been a part of .NET for a long time. Unfortunately, there are a couple of problems:
I was honored to have been on CodeCast Episode #2. While there, I talked about my past, how I got into programming, and the decision tree that led me to use Xamarin's technologies. After those discussions, I did a demo on oAuth authentication to Twitter via Xamarin.Auth and Xamarin.iOS (iPhone) and then showed the code for doing the exact same thing in Xamarin.Android (Android). Hopefully, this is helpful to you as you look at, discussion, try, and do whatever on Xamarin's technologies.
One of the great things about the .NET Framework is that Microsoft has worked long and hard to improve many features. Since the initial release of .NET 1.0, there has been support for threading via .NET threads as well as an application-level threadpool. This provided a great starting point when compared to Visual Basic 6 and classic ASP programming. The release of.NET 4 brought significant improvements in the area of threading, asynchronous operations and parallel operations. While the improvements made working with asynchronous operations easier, new problems were introduced, since many of these operations work based on callbacks. For example:
- How should a developer handle error checking?
- The program flow tends to be non-linear. Fixing bugs can be problematic.
- It is hard for a developer to get an understanding of what is happening within an application.
The release of .NET 4.5 (and C# 5.0), in the fall of 2012, was a blockbuster update with regards to asynchronous operations and threads. Microsoft has added C# language keywords to take this non-linear callback-based program flow and turn it into a much more linear flow. Recently, Xamarin has updated Xamarin.Android and Xamarin.iOS to support async.
This article will look at how Xamarin has implemented the .NET 4.5/C# 5 support into their Xamarin.iOS and Xamarin.Android productions. There are three general areas that I'll focus on:
- A general look at the asynchronous support in Xamarin's mobile products. This includes async, await, and the implications that this has for cross-platform code.
- The new HttpClient class that is provided in .NET 4.5/Mono 3.2.
- Xamarin's extensions for asynchronous operations for Android and iOS.
FYI: Be aware that sometimes the OpenWeatherMap API breaks, for no reason. I found this out after I shipped the article in.
Real Estate is all about location, location, location. Mobile is about maps, location and maps. Maps are an excellent mechanism to communicate information about locations. Maps are graphical, and you know that a picture is worth a thousand words. When users are mobile, presenting a user with a map provides him with easy-to-understand location information in a graphical format. Android provides full mapping support to present maps to users along with a programmable API. In this article, I'll introduce the mapping and location APIs in Mono for Android.
The following is a link to my talk on Mapping & Location in iOS and Android at Xamarin Evolve 2013. Obviously, the talk is centered on MonoTouch, aka Xamarin.iOS, and Mono for Android, aka Xamarin.Android. In this talk, I cover the native functionality of each platform. In addition, I cover Google Maps for iOS SDK. I hope that you find the talk to be helpful.