4. Die Kurze Geschichte der
Zeit
Surface
Windows NT Vista Windows 8
WinRT
System32/
System32 WinRT
Windows 95
WP8
DOS Windows CE/
Win Mobile WP7
Embedded
WP8 Runtime
System32/CE
5. Demo
As Runtime
(Store App)
WinRT
As API
(Desktop App)
6. Platform Compatibility
o WP7 and WP7.1 Apps run on WP8!
o No general breaking changes
o Existing code is emulated in Quirks-
Mode
o Some API differences
example:
XmlSerializer
WP8 must have a default constructor.
WP7 quirks: It is not necessary to have a default
constructor
o Code after Rebuild targets WP8 platform
8. Upgrade
o In Solution Explorer, use the Upgrade
to Windows Phone 8.0 command.
o In the project designer, change the
Target Windows Phone OS Version
value to Windows Phone OS 8.0.
10. Emulator
• Hardware-assisted virtualization supported and
enabled in the BIOS
• Second Level Address Translation (SLAT)
supported by the BIOS
• Hardware-based Data Execution Prevention
(DEP) supported and enabled in the BIOS
http://developers.de/blogs/damir_dobric/archive/2012/10/14/windows8-error-hypervisor-is-not-running.aspx
17. Common API-s
Native API WinRT API
Networking
DirectX 11.1
Sensors
XAudio2 Proximity
Storage
MediaEngine
DataSaver/Connection Manager
STL Location
Touch
CRT
Online Identity
WinSock Keyboard
Launchers & Choosers
In-App Purchase
Sensors
Threading
Base Types/ Windows.Foundation
18. New APIs
o Bluetoth
o Advanced Capture
o Lence control
o Photo and Media enhencmets
o LongListSelector
o Subset of WinRT storage API
o Data Sense API
o DirectX and native audio and media
o File and protocol associations
o In-App purchasing
o Location tracking in Background
o App as Lock Screen
23. Demo
Windows Phone 8
JavaScript
Web App
jQuery
on Phone
http://wpwidgetlibrary.codeplex.com/
24. Threading
o OS 7.1, apps run on a single core, and
the scheduler is less aggressive in time-
slicing
o OS 8, apps run on multiple cores and the
scheduler is more aggressive in time-
slicing threads.
Raise conditions and concurrency bugs
easier to achieve
25. Platform Targeting
o Single OS 7.1 version which runs on
both. No new features are supported.
Runs in quirks
o Create separate copy for 7.1 and 8.0
o Create separate copy with shared files
30. Enterprise Device
Enrollment
o Enterprise Enrollment
o Company Account
o Symantec Verification
o Corporate Signing Certificate
o Management
o System Center
o InTune
o Token Distribution
o AETGenerator
generates Application Enrollment Token (AET)
.aetx
o EnterpriseInstall.exe
o Enrolles Token
o Distributes XAP
o EnterpriseValidation.exe
o Periodically sends Device ID, installed apps to MS Server to validate
enterprise.
o Enterprise Developer API
o query what apps are installed for enterprise,
o start an enterprise app installation
o query pending enterprise app installation
Ecosystem Overview There are some general steps that enterprises must follow to establish an enterprise account, enroll devices and distribute apps to their enrolled devices. The following list describes these. An enterprise establishes an account on the developer site and is verified by SymantecAn enterprise receives a certificate, which they use to create an enrollment token to enroll devices in their enterprise.The enterprise can use the same certificate to sign apps and deploy them to their app portal.Users within the enterprise install the enrollment token on their phone, either through an OMA DM system or manually.Once a phone is enrolled in the enterprise, the employee can visit an enterprise specific app portal and download and install apps.Enterprises can query a phone for the enterprise-specific apps installed on the device.Enterprise Enrollment Enterprises will be required to establish a company account on Windows Phone Dev Center. As a part of establishing the account the enterprise will undergo a verification process with Symantec. Once an enterprise account has been established, a certificate and tools are provided to enterprises to enable them to sign apps and complete other tasks specific to enterprise app distribution. Enterprise Enrollment Token Distribution An enterprise can either manage Windows Phones using an OMA-DM management system such as System Center or InTune or they can use a set of tools provided by Microsoft to manage their phones manually. Following is a list of some of these tools and their purpose. AETGenerator Generates an Application Enrollment Token (AET) for distribution to a phone.EnterpriseInstall.exe Provides enterprise token enrollment and distribution of one enterprise XAP. This typically application launches when a user clicks a link or attachment that contains the application enrollment token (.AETX) file.EnterpriseValidation.exe Enables enterprise-enrolled phone to periodically send a message to a Microsoft server to report device ID, enterprise apps installed on the phone and the validity of the enterprise.Enterprise Developer APIs