Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

WIndows Embedded Compact 2013 – What’s news

2.792 visualizaciones

Publicado el

Overview about the Windows Embedded Compact 2013

Publicado en: Tecnología, Empresariales
  • Sé el primero en comentar

WIndows Embedded Compact 2013 – What’s news

  1. 1. Windows Embedded Compact 2013 What’s news Mirco Vanini Microsoft® MVP Windows Embedded
  2. 2. Agenda       WEC 2013 - What’s it Development overview Building WEC Native Development Managed Development XAML for Windows Embedded
  3. 3. WEC 2013 - What’s it Windows Embedded Compact 2013 (AKA WinCE) is Microsoft’s platform for small-footprint devices that need hard, real-time performance and silicon flexibility with ARM and x86 Familiar tools like Visual Studio and Expression Blend allow you to create attractive and intuitive user interfaces, and bring differentiated devices to market faster than ever before. Real-time operating system supports an array of hardware requirements and key processor architectures, including x86 and ARM, to power everything from tiny controls to fully automated factories. Improved file-system performance gives companies confidence that their devices will always be available; the one -tier security feature is SDL compliant, with reliable wireless connectivity and networking.
  4. 4. What’s news  Hard real-time e small footprint  x86 & ARM v7 Cortex-A (Thumb2)  VS2012 support for C# / C++ / XAML for Embedded  Fast boot (2s from power on)  Kernel update: increased file system performance
  5. 5. Development overview  Move to Visual Studio 2012         Provides significantly improved IDE New Arm complier (use desktop compiler) Last C Runtime Library (CRT) Application Builder For WEC 2013 (replace VS for Device) Platform Builder moved to VS2012 (Update 2) VS >= Professional version Native, Managed, XAML for Embedded Integrated deployment and debugging infrastructure, Ethernet connectivity to remote device
  6. 6. Application Development Setup  Windows Embedded Compact 2013 toolkit      Install on VS 2012 Update 2 Install Application Builder for WEC 2013 Install Windows Embedded XAML Tools Install Blend Templates Install SDK created by Platform Builder 2013 License Terms (Compact
  7. 7. The Board Support Package  Layer for OEM code written to port Windows Embedded Compact to hardware  OAL – OEM Adaption Layer  Drivers - code for supporting hardware peripherals  … Board Support Packages
  8. 8. Set up a virtual test device Use Hyper-V to create a virtual machine (Compact 2013)  Visual Studio and Platform Builder run directly on the physical computer  Platform Builder connects to the virtual machines through a virtual network or virtual switch  The virtual network or virtual switch maps to a network adapter on the physical computer and has access to a DHCP server  The virtual machines run Compact 2013, and they obtain their IPv4 addresses from the DHCP server.
  9. 9. Platform support for Application Debug  Add the “Application Builder Debugging Support” component  Add “Remote Tool Support”  Add “Network Utilities”
  10. 10. demo
  11. 11. Connection to the Device  Uses “CoreCon” as the connection (connects via network)  New target connectivity device-side files  Use OSDesign.bib file C:Program Files (x86)Common FilesMicrosoft SharedEmbedded ToolsCoreCon11.0Targetwce800x86
  12. 12. Connection to the Device  Query IP device address  Configure IP Address in VS Project  Launch device side  ClientShutdown3 (optional)  ConManClient3  CMAccept3  Start debugging (3 min timeout)
  13. 13. demo
  14. 14. Create a Developer WM Windows Embedded CE DiskPrep PowerT
  15. 15. demo
  16. 16. Using an SDK for an OS Image  You can create a project for an application that you will develop and test on a stand-alone virtual device that includes the run-time image in a virtual drive or on a device that has the runtime image copied into flash memory.  This type of project does not require Platform Builder because you do not need to download an run-time image to the device or the virtual device to test a change in your application code.
  17. 17. Native Application Development  Move to latest Microsoft C++ Compiler  C++11 standards (subset)  Provider consistency with desktop  Leverage performance work done by desktop team  C++ improvements  Lambda functions  Strongly typed and scoped enumeration support  “auto” keyword  Last version of runtime libraries  C++ runtime  MFC  ATL & STL
  18. 18. demo
  19. 19. Managed Application Development  NETCF 3.9 (based on the NETCF version that shipped with Windows Phone 7.5)  New generational garbage collector (5060% drops in GC time)  NETCF runtime is now multi-core safe  Sharing server features  Reduce working set  Improve app launch  Framework assemblies shared across app domains  ARM VFP instructions.  Source compatible with NETCF 3.5
  20. 20. Managed Application Development  Requires SDK exported from Platform Builder (unlike earlier versions of NETCF)  Requires rebuild of managed code from earlier releases  Exports from COREDLL are not backward compatible (P/Invokes)
  21. 21. demo
  22. 22. XAML for Windows Embedded  Data binding expanded      UI to UI data binding now supported DataContexts con now be set in XAML Data Binding resource references Data Binding type conversion Data Binding indexing  New Blend triggers supported     ChangePropertyAction ControlStoryBoardAction GoToStateAction RemoveElementAction  XAML for Embedded development free from PB
  23. 23. XAML for Windows Embedded  Windows Embedded XAML Tools limitations     It does not create XAML files It only generates C++ code It does not support custom controls It does not generate C++ code for the following XAML elements:            ControlTemplate DataTemplate FrameworkTemplate ItemsPanelTemplate MediaElement Resources RenderTransform Storyboard Style VisualState VisualStateGroups
  24. 24. XAML for Windows Embedded  Create initial user interface designed in Blend for Visual Studio 2012  Create XAML project in Visual Studio (C++)  Compile and debug as a native application  Update to U/I brought in with XAML tools in VS2012
  25. 25. demo
  26. 26. Q&A
  27. 27. Links Windows Embedded Compact 2013 Windows Embedded Product Downloads MSDN - Windows Embedded Compact Windows Embedded Blog Embedded101 Microsoft Intelligent Systems Video
  28. 28. Contatti o feedback su: • o codice feedback: • DEC06 Blog Email Web Twitter @MircoVanini feedback 10