2. VERONIKA KOLESNIKOVA
• BS in Applied Computer Science and Economics (graduated with honors)
• MS in Information Technology
• 3.5 years QA Experience
• 5 years development experience
• C#, .NET, SQL, Xamarin, .NET-based CMSes like EPiServer, Sitecore
• PHP, MySQL, Drupal, RoR
• Hobbies: dancing, travelling, aerial yoga
3. WHAT IS XAMARIN?
• Xamarin is a Microsoft-owned San Francisco, California-based software company
• With a C#-shared codebase, developers can
write native Android, iOS, and Windows
apps
4. Founded in
May 2011
In December
2012 -
Xamarin.Mac
In February
2013 -
Xamarin 2.0
On February
24, 2016 –
Microsoft
acquired
Xamarin
Microsoft
Build 2016 -
open-source
the Xamarin
SDK, VS
integration
A LITTLE BIT OF HISTORY
https://github.com/xamarin
6. XAMARIN FORMS
• Xamarin.Forms is a framework that allows developers
to rapidly create cross platform user interfaces.
It provides it's own abstraction for the user interface
that will be rendered using native controls on iOS,
Android, Windows, or Windows Phone
7.
8. XAMARIN VS XAMARIN.FORMS
Xamarin.Forms is best for:
• Data entry apps
• Prototypes and proofs-of-concept
• Apps that require little platform-
specific functionality
• Apps where code sharing is more
important than custom UI
Xamarin.iOS & Xamarin.Android are
best for:
• Apps that require specialized
interactions
• Apps with highly polished design
• Apps that use many platform-
specific APIs
• Apps where custom UI is more
important than code sharing
9. NATIVE FUNCTIONALITY
Device class Dependency Service
double top;
switch (Device.RuntimePlatform)
{
case Device.iOS:
top = 20;
break;
case Device.Android:
case Device.WinPhone:
case Device.Windows:
default:
top = 0;
break;
}
layout.Margin = new Thickness(5, top, 5, 0);
11. XAMARIN ON AZURE
Xamarin Azure App Service On-Premises
• Smartphone, tablet
and watch user
experience
• Azure SDKs for data
sync, storage, push
notifications and API
access
• Single-sign-on
• Reusable web APIs for
mobile, web,
integration and B2B
• Extend on-premises
databases and systems
to mobile and cloud
(VPN, Hybrid
Connections)
• Identity – Active
Directory
• Existing databases
• Existing systems
12. XAMARIN MOBILE APPS AND AZURE:
WAYS OF INTEGRATION
• Azure Active Directory
• User authentication
• Azure Databases, both SQL and non-SQL
• Offline synchronization
• Web services
• Push notifications
• Continuous integration (delivery), testing and special deployment
• All benefits of Azure: monitoring, scaling, alerts, billing, backup, load balancing, etc.
14. ADD AZURE CONNECTION TO EXISTING
XAMARIN.FORMS PROJECT
public static MobileServiceClient MobileService =
new MobileServiceClient(
"https://basicapp123.azurewebsites.net"
);
using Microsoft.WindowsAzure.MobileServices;
18. USEFUL LINKS
• https://developer.xamarin.com/guides/xamarin-forms/getting-started/
• Introduction to Xamarin.Forms by Jim Wilson on Pluralsight:
https://app.pluralsight.com/library/courses/xamarin-forms-
introduction/table-of-contents
• https://github.com/Veroni4ka/Xamarin-Todo-Form
• iOS and Android development courses and articles
• Feel free to reach me through LinkedIn:
https://www.linkedin.com/in/vkolesnikova/
Hinweis der Redaktion
Mono, Mono Android and Mono Touch , which are cross-platform implementations of the Common Language Infrastructure (CLI) and Common Language Specifications (also known as Microsoft .NET) The name Xamarin comes from the name of the Tamarin monkey, replacing the leading T with an X. This is in line with the naming theme used ever since Xamarin was started.
Mono, Mono for Android, Mono Touch , which are cross-platform implementations of the Common Language Infrastructure (CLI) and Common Language Specifications (often called Microsoft .NET)
The Device class contains a number of properties and methods to help developers customize layout and functionality on a per-platform basis
If using Visual Studio, right-click your project and select 'Manage NuGet Packages' search for the Microsoft.Azure.Mobile.Client package, and click 'Install.'
In your main Activity file, add a 'using Microsoft.WindowsAzure.MobileServices;' statement. Then copy and paste in the following code:
The Xamarin Profiler integrates seamlessly with your existing Xamarin toolchain to collect information about your Xamarin apps. Use it to find memory leaks, resolve performance bottlenecks, and add polish to your apps before getting them out the door. Toolbar – Located at the top of the profiler, this offers options to start/stop profiling, select a target process, view the running time of the app, and select the split views that compose the profiler application.
Instrument List – This lists all instruments loaded for the profiling session.
Plot Chart – These charts relate horizontally to the relevant instruments in the instrument list. A slider (shown beneath Time Profiler) can be used to change the scale.
Instrument Detail area - Contains data being displayed by the selected view of the current Instrument. We will look at these views in more detail in the section below.
Inspector View – This contains sections that can be selected by the segmented control. The sections are dependent on the instrument selected, and includes: Configuration Settings, Statistics, Stack Trace information, and Path to roots.
