Windows Phone 8 Advanced Developers Conference
Download as PPTX, PDF1 like585 views
Windows Phone 8 introduced a new "Runtime 8" platform that provides backwards compatibility with Windows Phone 7 apps. It allows code sharing between Windows Phone 8, Windows 8, and portable class libraries. The Windows Phone 8 SDK added new APIs, supported additional languages like JavaScript, and improved areas like multitasking, networking, and in-app purchasing.
Windows Phone 8 Advanced Developers Conference
- 1. DEVELOPMENT FOR WINDOWS PHONE 8 Damir Dobric
- 2. AGENDA Platform Platform Evolution Compatibility “Runtime 8” Emulator WP8 API Platform App Model Targeting Code Sharing/ Mobile Speech Services
- 3. Evolution
- 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
- 7. The dream or reality?
- 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.
- 9. Demo Windows Phone 8 Hello World
- 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
- 11. Resolution Scaled Resolution Aspect ratio resolution WVGA 480 × 800 15:9 480 × 800 WXGA 768 × 1280 15:9 480 × 800 720P 720 × 1280 16:9 480 × 853
- 14. Runtime 8
- 15. Runtime 8
- 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
- 20. Your Apps Your way
- 22. Project Templates o C# (HTML5) o XNA o C++ o HTML5
- 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
- 26. Demo Windows Phone 8,Windows 8 Code Sharing Portable Linked Files Library Camera Accelerometer
- 27. Network Improvements o Socket Listeners (Incoming) Windows.Networking.Sockets o IPv6 o Winsock Support o Proximity API
- 28. In-App Purchasing Class Member Description LoadListingInformationByProductIdsAsync(ListingInformatio CurrentApp n productIds) LoadListingInformationByKeywordsAsync(ListingInformation CurrentApp keywords) CurrentApp void ReportProductFulfillment(string productId) ProductLicense bool IsConsumable { get; } ProductListing string Description { get; } ProductListing IEnumerable<string> Keywords {get;} ProductListing ProductType ProductType {get;} ProductListing string Tag {get;} ProductListing Uri ImageUri { get; }
- 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
- 32. Demo Speech
- 33. Demo Speech
- 35. Demo Windows Phone 8 Windows Azure Mobile Services
- 36. Where to start? WP8 MSDN Documentation http://msdn.microsoft.com/en- us/library/windowsphone/develop/ff402535(v=vs.105).aspx WinRT: http://de.slideshare.net/ITCamp/itcamp-2012-raffaele-rialdi-introduction-to- winrt
- 37. Recap Platform Platform Evolution Compatibility “Runtime 8” Emulator WP8 API Platform App Model Targeting Mobile Code Sharing Services
- 38. Differences
Editor's Notes
- #7: Platforn, Clr and App compatibility
- #31: 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