1 / 18

Building world-ready Metro style apps with XAML

APP-528C. Building world-ready Metro style apps with XAML. Tim Heuer Program Manager Microsoft Corporation. Agenda. What’s new/different for XAML localization How Visual Studio tools will help API versus markup a pproaches Element versus layout a pproaches. XAML localization h istory.

paul2
Download Presentation

Building world-ready Metro style apps with XAML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. APP-528C Building world-ready Metro style apps with XAML Tim Heuer Program Manager Microsoft Corporation

  2. Agenda • What’s new/different for XAML localization • How Visual Studio tools will help • API versus markup approaches • Element versus layout approaches

  3. XAML localization history • BAML • RESX • Data binding approaches

  4. Design and plan for localization • Start right and plan for localization • Organize assets in Visual Studio • Use element markup in XAML to prepare ahead

  5. Planning ahead makes localizing your XAML app later as easy as providing new resources and re-packaging the app.

  6. Visual Studio project organization • Introduction of RESW file and Editor (new for Native) • Understanding path-based mapping of project resources • Native project system nuances due to filters versus folders

  7. API differences for resources • For .NET developers • No strongly-typed class representation using RESX • No embedded resources in DLLs • For native developers • No .rc files • NEW for both • Use Windows Runtime resource APIs to extract string/path resource information from package

  8. Extracting string resources (new) • C# • ResourceLoaderresources = newResourceLoader(); • stringwelcomeText = resources.GetString("WelcomeText"); • C++ • ResourceLoader^ resources = refnewResourceLoader(); • String^ welcomeText = resources->GetString("WelcomeText");

  9. Using new markup support • x:Uid support for element-based localization • Have the XAML parser works for you • Same for native or managed • Advanced RESW annotation for user controls

  10. Localizing a TextBlock • <Grid x:Name="LayoutRoot" Background="#FF0C0C0C"> • <TextBlock x:Uid="MyTextBlock"FontSize="72" /> • </Grid>

  11. Full layout localization • New mechanism allows you to wholesale replace pages • RTL locales • Special cultural considerations • Requires more forethought and care due to markup compile

  12. demo Using x:Uid for localization in XAML

  13. Testing your localization • Using ResourceContext to test • Changing ultimate fallback language

  14. Related sessions • [411] Reach a worldwide audience by building a world-ready app (must see)

  15. Further reading and documentation • Windows Developer Center • http://go.microsoft.com/fwlink/?LinkID=227201 • Windows SDK Samples • http://go.microsoft.com/fwlink/?LinkId=221708 • Contact info – xamlfeedback@microsoft.com

  16. thank you Feedback and questions http://forums.dev.windows.com Session feedbackhttp://bldw.in/SessionFeedback

  17. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

More Related