Downloaded 38 times
Uploaded byClemente Giorio
Develop a Windows 10 App. Deploy it on PC, Phone and Raspberry Pi.
The document outlines the development of a Windows 10 app using the Universal Windows Platform (UWP) to deploy on multiple devices, including PCs, phones, and Raspberry Pi. It emphasizes the unified app model, showcasing how apps are designed to target the platform rather than individual operating systems, and details the required APIs and development environment. Additionally, it includes practical examples and resources for setting up and deploying apps across various device families.
More Related Content
![O potencial Mobile [GUDAY 2016]](https://cdn.slidesharecdn.com/ss_thumbnails/guday-dwildt-dscheibler-o-potencial-mobile-160415041416-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Develop a Windows 10 App. Deploy it on PC, Phone and Raspberry Pi.
Develop a Windows 10 App. Deploy it on PC, Phone and Raspberry Pi.
- 1. MOBILE CAMP -NAPOLI Develop a Windows 10 app Deploy it on PC, Phone and Raspberry Pi Clemente Giorio
- 2.
- 3. Overview on UniversalWindows Platform How to Develop a simple UWP app Deploy on PC Agenda Deploy on Phone Deploy on Raspberry Pi 2
- 4.
- 5. One Hardware platform Universalhardware driver Standard network and I/O One App Mode One Windows Kernel
- 6.
- 7. One Windows Desktop SKU PC 2 in1 Mobile SKU Tablet Phablet Phone Xbox SKU Xbox IoT SKU Band IoT headless SKU Raspberry Pi Home Automation Surface Hub SKU Surface Hub Holographic SKU HoloLens
- 8. Each family addsfeatures to the one it inherits
- 9. Easy for usersto get & stay current Unified core and app platform Windows 10 Converged OS kernel Converged app model
- 10. Phone Small Tablet 2-in-1s (Tabletor Laptop) Desktops & All-in-OnesPhablet Large Tablet Classic Laptop Xbox IoTSurface Hub Holographic Windows 10
- 11. One Store + OneDev Center Reuse Existing CodeOne SDK + Tooling Adaptive User Interface Natural User Inputs One Universal Windows Platform
- 12.
- 13. One Windows Desktop SKU PC 2 in1 Mobile SKU Tablet Phablet Phone Xbox SKU Xbox IoT SKU Band IoT headless SKU Raspberry Pi Home Automation Surface Hub SKU Surface Hub Holographic SKU HoloLens
- 14. Apps don't targetOperating System, Apps target the platform
- 15. Universal Windows 8.1app #if WINDOWS_APP ResourceLoader loader = new ResourceLoader(); string about = loader.GetString("SettingsLabel/Text"); string privacy = loader.GetString("PrivacySettings/Text"); string options = loader.GetString("Settings/Text"); ISettingsService settings = container.RegisterSettingsService(); settings.RegisterFlyoutCommand<AboutViewModel>(about); settings.RegisterFlyoutCommand<PrivacyPolicyViewModel>(privacy); settings.RegisterFlyoutCommand<SettingsViewModel>(options); #endif
- 16.
- 17. The Universal WindowsPlatform can update at its own cadence
- 18. Phone Device Xbox Device Desktop Device Windows Core Universal WindowsPlatform Windows App
- 19. Phone Device Xbox Device Desktop Device Windows Core Universal WindowsPlatform Windows App Phone extension Xbox extension Desktop extension
- 21. Extensions don't invalidate binarieson other devices
- 22.
- 23. Traditional Microsoft technologiesare not the only way to create Windows apps
- 24. Windows 10 operating system Bridgingtechnologies Win32 desktop Web hosted Java Android Obj.C iOS Universal Windows Platform WWAC++ & CX .Net languages HTML DirectX XAML C++ .Net languages MFCWFWPF .Net runtime
- 25.
- 26. Bridges bring moreapps to the Windows platform
- 27.
- 28. Users love appsthat work great on all their devices
- 29. var api ="Windows.Phone.UI.Input.HardwareButtons"; if (Windows.Foundation.Metadata.ApiInformation.IsTypePresent(api)) { Windows.Phone.UI.Input.HardwareButtons.CameraPressed += CameraButtonPressed; }
- 30.
- 31. UAP Windows Core WindowsCore Windows Core Windows Core UAP UAP UAP Desktop Mobile Xbox More…
- 32. The device familiesyou choose determines which APIs you can call freely
- 33. One simple, unified,integrated development environment
- 34.
- 35.
- 36.
- 37.
- 39. The code Deploy onPC Deploy on Phone Emulator Deploy on Raspberry Pi 2
- 41.
- 45. Windows Embedded Pre-ReleasePrograms Setup Raspberry Pi 2 Boot Windows 10 IoT Core Insider Preview
- 47.
- 59.
- 62.
Editor's Notes
- #10 Platform convergence has been a journey which ends today with Windows 10 We started by using the same Internet Explorer code + engine on Windows Phone 7.5 and Xbox 360; and we started implementing the Microsoft modern design language. With the release of Windows 8, we converged the Windows kernel (which aligns, among other things, the HAL and driver models). Windows Phone 8 took advantage of new lighter-weight kernel to enable multiple CPUs and other improvements, and the Xbox One was built on top of Windows 8. Xbox also introduced xJS, Xbox’s version of WinJS so developers could write apps in HTML/WinJS the same framework as available on Windows 8. With the release of Windows Phone 8.1 the runtimes from Windows 8.1 and phone came together as well – continuing up the Windows stack and building upon the kernel convergence that happened in 8.0 – aligning the app models and API set, bringing 90%+ API convergence and unification/convergence of things like Windows Notification Services, back-stack behavior, sharing contracts, live tiles, etc. With Windows 10, we bring complete the unification of Windows families, and now provide a Windows core that can be used on embedded and IoT devices. Background data: 9/15/11 Windows Phone 7.5 10/26/12 Windows 8 10/29/12 Windows Phone 8 10/18/13 Windows 8.1 11/22/13 Xbox One 4/8/14 Windows 8.1 Update 3/26/14 Windows Phone 8.1
- #12 To bring the family together, Windows 10 is built upon a unified core (the Windows core) and a unified app platform (Universal Windows platform), meaning that all of our device families run Windows at their core. This provides the consistency that users need and the tailored experiences desire. Gone are the days of Microsoft maintaining a number of code-bases that works to build bridges across silos; Windows has evolved to do that itself. And gone are the days of ISVs doing this as well – targeting Windows provides a single roadmap to the billion+ Windows screens. Enabling this consistent, yet tailored, Windows experience are a number of services: Adaptive UX: User interface design that adapts and reacts to the device family it’s running on Natural user inputs: Speech, natural ink, gesture and facial recognition Cloud-based intelligent services: Cortana AI, personal hubs, OneDrive, Office 365, Windows notification services, credential locker Windows Store: Universally available apps and games, digital media For the app builder, this also means that you can build one Windows solution that runs across all of the Windows device families, and use these Windows services to tailor your experience at runtime.
- #41 Add a reference to the Windows IoT extension SDK namespaces like Windows.Devices.Gpio Windows Universal->Extensions->Windows IoT Extension SDK
- #45 Set HelloWorld as the Startup App You can also set this HelloWorld app to be the ‘Startup App’ for your Windows IoT Core device, so that when the device reboot, it will start HelloWorld automatically. To do so, you’ll need to run a command line utility called iotstartup on the Windows IoT Core device. We will do this using PowerShell. Start a PowerShell (PS) session with your Windows IoT Core device as described here. From the PS session, type: [192.168.0.243]: PS C:\> iotstartup list HelloWorld and you should see the full name of our HelloWorld UWP application, i.e. something like: Headed : HelloWorld_n2pe7ts0w7wey!App the utility is confirming that HelloWorld is an ‘headed’ application, and is installed correctly. Now, it’s easy to set this app as the ‘Startup App’. Just type the command: [192.168.0.243]: PS C:\> iotstartup add headed HelloWorld The utility will confirm that the new Startup headed app is now HelloWorld: AppId changed to HelloWorld_n2pe7ts0w7wey!App Go ahead and restart your Windows IoT Core device. From the PS session, you can issue the shutdown command: [192.168.0.243]: PS C:\> shutdown /r /t 0 Once the device has restarted, you’ll see HelloWorld start automatically. At this point, you can revert back to using the DefaultApp as your ‘Startup App’. Just type the command: [192.168.0.243]: PS C:\> iotstartup add headed DefaultApp The utility will confirm that the new Startup headed app is now DefaultApp: AppId changed to DefaultApp_cw5n1h2txyewy!App
- #46 Windows Embedded Pre-Release Programs: https://connect.microsoft.com/windowsembeddedIoT/Downloads/DownloadDetails.aspx?DownloadID=57782 Set your Device http://ms-iot.github.io/content/en-US/win10/SetupRPI.htm dism.exe /Apply-Image /ImageFile:flash.ffu /ApplyDrive:\\.\PhysicalDriveN /SkipPlatformCheck Using PowerShell to connect and configure a device running Windows IoT Core http://ms-iot.github.io/content/en-US/win10/samples/PowerShell.htm
- #50 Windows 10 IoT Core Command Line Utils http://ms-iot.github.io/content/en-US/win10/tools/CommandLineUtils.htm
- #55 Hardware interfaces for the Raspberry Pi 2 are exposed through the 40-pin header J8 on the board. Functionality includes: 13x - GPIO pins 2x - SPI buses 1x - I2C bus 2x - 5V power pins 2x - 3.3V power pins 8x - Ground pins