Developing Universal

Windows Apps with C#

and XAML
Jerry Nixon | Microsoft Developer Evangelist
Daren May | President & Co-founder, Crank211

Hi. Im Jerry Nixon | Colorado

Microsoft Developer Evangelist
Reaching Professional & Student Communities
Teaching Developers about Windows Phone
Teaching Developers about Windows 8
Teaching Developers about XAML
http://jerrynixon.com
@jerrynixon

Hi. Im Daren May | @darenmay

President & Co-founder, Crank211
We design and build digital products with a business
mind, technology muscle, and a creative soul.
Windows Platform Developer MVP

Prior to starting Crank211

CTO and VP Operations for software consultancy
Practice lead for EMC Consulting
Leveraged Microsoft technologies since
Visual Studio .NET betas
Developing XAML-based solutions since
the heady days of Avalon (the early name for WPF)

Setting Expectations
Target Audience
Windows Store Developers
Windows Phone Developers

Suggested Prerequisites/Supporting Material

Programming in C# JumpStart
Essentials of Developing Building Windows Store Apps with
C#/XAML
Advanced Windows Store Apps with C#/XAML
Designing your XAML UI with Blend

Join the MVA Community!

Microsoft Virtual Academy
Free online learning tailored for IT Pros and Developers
Over 2M registered users
Up-to-date, relevant training on variety of Microsoft
products

Earn while you learn!

Get 50 MVA Points for this event!
Visit http://aka.ms/MVA-Voucher
Enter this code: DevUnivWinAppsC1 (expires 10/31/2014)

Course Topics
01 | Building Universal Windows
Apps - Part 1
02 | Building Universal Windows
Apps - Part 2

08 | Security
09 | Local data

03 | UWA Design

10 | Communication

04 | Introducing Solarizr

11 | View services

05 | Building a Web Service

12 | Advanced features

06 | Prism - Part 1

13 | What else might we have

done?

07 | Prism - Part 2

This code is on CodePlex

http://xaml.codeplex.com

01 | Building Universal
Windows Apps Part 1
Jerry Nixon | Microsoft Developer Evangelist
Daren May | President & Co-founder, Crank211

Module agenda
The universal promise
The user perspective
The store perspective
The developer perspective

The universal promise

What is a universal app?

You can build an app that targets
Windows and Windows Phone
It is not (currently):
A single binary
A non-Windows binary (Xamarin) application
Targeting iOS
Targeting Android

An HTML/JavaScript (Cordova) application

The user perspective

What does it mean to be universal?

The consumer promise
Similar theme
Common experience
Shared authentication
Shared data/profile
Single app purchase
Single IAP purchase

Tailoring the experience

The store perspective

What does it mean to be universal?

The Windows Store perspective
Shared package full name
Single app purchase
Single IAP purchase
Roaming data
Shared notification channel

DEMO
Universal App in Windows Store

Buy a universal app on Windows and its

available on Phone without additional purchase

Buy an in-app entitlement on Windows and its available on Phone without additional purchase

Register the same Push Notification channel against both the Windows and Phone app

Save roaming data in Windows and that same

Data is available in the Phone version

The developer perspective

What does it mean to be universal?

The Visual Studio perspective
Shared project-type
A new feature or bug in one
project, everything is updated

Still possible to tailor

Reusing code is meaningful
because of unified APIs

The Windows Runtime API & Microsoft SDKs are

around 90% converged, and closing

DEMO
Making Windows 8 projects
Mixed
Shared

;-)

Universal Apps supports

C#, C++, and JavaScript

Windows Phone Silverlight and Windows apps

can share a Package Family Name

Existing Windows 8 apps can be

migrated to shared projects

Module recap
The universal promise
Code sharing strategies

2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered
trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of
Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a
commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT
MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.