How to start with Xamarin from basic steps

Here are few steps prepared by my colleague so hope it will help you to start with Xamarin basic app.


Xamarin Setup Requirements
  • Visual Studio 2015 with full features.
  • Java SDK 1.7 Kit.
  • Window Operation system 7, 8
  • Xamarin Installer
  • Xamarin Android Player Emulator.
Xamarin Introduction
Build native UIs for iOS, Android and Windows, from a single, shared C# codebase.
URL

Xamarin Forms
URL



Introduction
Take code sharing to the next level with Xamarin.Forms. Intro to iOS and Android teach you how to share core logic across platforms, and Xamarin.Forms lets you define a singular UI that creates a native user experience for iOS, Android, and Windows.
          
Xamarin Pages Types
Page is an Abstract class used to define a single of content.
  1. Content
  2. Master detail
  3. Navigation
  4. Tabbed
  5. Carousel
Views
View is the base class for all visual control, Most Standard controls are listed below:
  • Label
  • Image
  • searchBar
  • Entry
  • Progress Bar
  • Activity Indicator
  • Button
  • Slider
  • Open Gridview
  • Editor
  • Stepper
  • Webview
  • Datepicker
  • Switch
  • Listview
  • Box view
  • Frame
  • Picker
Configuration Manager Option
Any CPU >> Configuration environment
You can set Active Solution platform for three solutions.
1. Window simulator= X86
2. Android = ARM
3. IOS = IPhone Simulator

How to create Xamarin Form Project Solutions
File >> new project >> Mobile APPS >> Blank App (Xamarin Form Portable)
Click on blank app application will be created with four solutions.
Add Xamarin Android player into VS 2015
Tools >> Android >> Android Adb command prompt >> write Adb >> Adb connect IP address
4 Solutions Added Successfully:
  • Portable Solution, Platform specific projects, Platform Specific, Android, Xamarin forms.
  • Android
  • IOS
  • Window Phone
Xamarin Form Layout Container
Layout Containers organize child elements based on specifics rules.
.XAML Layout
1. Stack Layout - This layout is used for typical form style layout
  • Vertical option
  • Horizontal option
  • Spacing
  • padding
2. Absolute layout
3. Relative layout
4. Grid Layout

Xamarin Form Architecture
Xamarin forms has two projects that work together to provide the logic + UI for each executable
1. Portable class
  • Shared Across all platform
  • Limited access to .net APIs
  • Want most of our code
2. Platform Specific Project
  • 1 per platform
  • Code is not shared
  • Full access to .Net apis
Changing the UI per platform
  • Device On platform allows you to fine tune the UI for each platform.
Can execute specific logic per platform using delegates for each platform.     
Detecting platform
Can use the static Device class to identify the platform and device style
  • Xamarin.forms.maps
  • Device.BeginInvoke.onmainthread
Use XAML in Xamarin
Views and Layout in Xamarin.Forms
Pages
Xamarin.Forms pages represent cross-platform mobile application screens. For more information about Pages, See
1. Content Page
2. MasterDetail page
3. Navigation Page
4. Tabbed Page
5. Templated Page
6. Carousel page
 
Layouts
Xamarin.Forms layouts are containers used to compose views into logical structures. For more information about Layouts, see
1. Content Presenter
2. Content View
3. Scroll view
4. Frame
5. Templated view
6. Stack layout
7. Gridlayout
8. Relative Layout
Views
Xamarin.Forms views are the controls displayed on the user interface, such as labels, buttons, and text entry boxes. For more information about Views, see
ActivityIndicator
BoxView
Button
DatePicker
Editor
Entry
Image
Label
Listview
Map
OpenGlView
Picker
ProgressBar
SearchBar
Slider
TableView
TimePicker
Webview
EntryCell
ImageCell
Switch Cell
TextCell
ViewCell
Cells
Xamarin.Forms cells are specialized elements used for items in a list, and describe how each item in a list should be drawn. For more information about Cells, see Xamarin.Forms Cells


Listview in Xamarin Form
The  Listview control is responsible for displaying a collection of items on the screen – each item in the Listview will be contained in a single cell.

Data Binding
Data binding connects two objects, called the source and the target. The source object provides the data. The target object will consume (and often display) data from the source object. For example, a Label (target object) will commonly bind its Text property to a public string property in a source object
Object (Source Property) <----------> Binding <--------> Property (UI Control Target)
XAML
The following code shows an example of performing data binding in XAML:
<Entry Text="{Binding FirstName}" ... />

Navigation
Xamarin.Forms provides a number of different page navigation experiences, depending upon the Page type being used. For ContentPage instances there are two navigation experiences:
There are two types of Navigation:-

Hierarchical Navigation
The Navigation Page class provides a hierarchical navigation experience where the user is able to navigate through pages, forwards and backwards, as desired. The class implements navigation as a last-in, first-out (LIFO) stack of Page objects.
Public App ()
{
  MainPage = new NavigationPage (new EmployeeListPage ());
}


Button button2 = new Button

{
Text = " Go to Image Demo Page ",
Font = Font.SystemFontOfSize(NamedSize.Large),
BorderWidth = 1
};
await Navigation.PushAsync(new LoginPage());



button2.Clicked += async (sender, args) =>
await Navigation.PushAsync(new ImageDemoPage());


Modal Navigation
Xamarin.Forms provides support for modal pages. A modal page encourages users to complete a self-contained task that cannot be navigated away from until the task is completed or cancelled.
Syntax
await Navigation.PushModalAsync(new LoginPage());
await Navigation.PopModalAsync();
Syntax is my UI
Create UI Login Page for Android, IOS and windows phone with Xamarin.Forms
Xamarin Controls
ActivityIndicator                BoxView             Button                DatePicker           Editor
Entry                                 Image                 Label                  Listview               Map
OpenGlView                     Picker                ProgressBar        SearchBar           Slider
TableView                        TimePicker          Webview             EntryCell             ImageCell
Switch Cell                       TextCell               ViewCell


Xamarin University Video Xamarin.Forms
Xamarin Android Player Download Link
XAML Form Page in Xamarin.Forms
·         https://developer.xamarin.com/guides/xamarin-forms/getting-started/introduction-to-xamarin-forms/
Create Login Screen Using XAML
Xamarin.Forms Architecture Diagram
IOS-------------->                   Android          -------------> Windows Phone
-------------------------------Core Layer -------------------->>>>>>>>>>>>>>>>>>>>
Business Layer
Service Access layer          Data access layer                   Data layer
Build native UIs
Each OS-specific application provides a different user-interface layer (implemented in C# with the assistance of native UI design tools):
  1. On iOS, use the MonoTouch.UIKit APIs to create native-looking applications, optionally utilizing Xamarin's iOS designer to create your UI visually.
  2. On Android, use Android.Views to create native-looking applications, taking advantage of Xamarin’s UI designer
  3. On Windows Phone you will be using the XAML/Silverlight presentation layer, using Visual Studio or Blend’s UI designer
  4. On Windows 8, use the Metro APIs to create a native user experience.
Xamarin Call Dial Demo
Installing Xamarin IOS on Window
Creating Xamarin form app in visual studio
First connect with mac using remote login. Tools IOS mac agent.
After successfully connected with mac agent. We will creating app in Xamarin.Forms.
File ----------> New project-----------> Cross platform-----------> Blank app (Xamarin.Forms portable)
App name-----------> WinSetupdemo
XAML Demo Project
XAML Practice Links
Alert Display
Redirect One Page to Another using navigation Page class
List view Control bind with List
Phone Number Dial App
Data Pages
Themes
Get Started with XAML in Xamarin Forms
Animation in Xamarin-forms
Android Splash Screen creation process
IOS project Setup











                  

Comments

Post a Comment

Popular posts from this blog

Executing PowerShell scripts from C#

Image
Please refer the original post from here http://blogs.msdn.com/b/kebab/archive/2014/04/28/executing-powershell-scripts-from-c.aspx I n today’s post, I will demonstrate the basics of how to execute PowerShell scripts and code from within a C#/.NET applications. I will walk through how to setup your project prerequisites, populate the pipeline with script code and parameters, perform synchronous and asynchronous execution, capture output, and leverage shared namespaces. Update 8/7/2014 : Here is the downloadable solution file. Update 11/5/2014 : Added a section on execution policy behavior. Prerequisites: First, ensure that PowerShell 2.0 or later is installed on the system you are developing on. The features used below will not be supported on PowerShell 1.0. Next, start by making a new console application (targeting .NET 4.0) in Visual Studio. In the solution explorer, add a project reference to the System.Management.Automation assembly * . On my machine (PowerShe...
Read more

HOW TO Use the NumericUpDown Control

HOW TO Use the NumericUpDown Control  Great help taken from  http://www.asp.net/ajaxlibrary/HOW%20TO%20Use%20the%20NumericUpDown%20Control.ashx NumericUpDown Demonstration NumericUpDown Description NumericUpDown is an ASP.NET AJAX extender that can be attached to an ASP.NET TextBox control to add "up" and "down" buttons that increment and decrement the value in the TextBox. The increment and decrement can be simple +1/-1 arithmetic, they can cycle through a provided list of values (like the months of the year), or they can call a Web Service to determine the next value. Page authors can also provide custom images to be used instead of the default up/down button graphics. Video - How Do I: Use the ASP.NET AJAX NumericUpDown Control? NumericUpDown Client Code Sample view plain copy to clipboard print ? < script   runat = "server" >        [System.Web.Services.W...
Read more

Exposing Agile Software Development Myths

Agile development is a movement that started 11 years ago and now is a commonplace discussion for software development teams. Prior to the signing of the Agile Manifesto in Utah in 2001 [endnote 1], the world was using a phased methodology called “Waterfall,” introduced (but not named) by Winston W. Royce [2], ironically trying to explain why that methodology was a bad idea. The methodology forced the completion of a phase in order to continue with the next one. That caused some problems since, no matter how hard the developers tried to gather all requirements and create a full system design, there was always the need in the following phases to go back and change things. Those regressions had a big impact on cost. The Agile principles tried to eliminate all the rigidity of Waterfall by focusing on more productive tasks, like working code over comprehensive documentation, adding more customer collaboration, enforcing individual interactions instead of tools and being a...
Read more