SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Bringing existing managed code into Metro style apps

Lucy avatar
Lucy
16 diapositives · 398 Views · Jan 09, 2012

TOOL-790C. Bringing existing managed code into Metro style apps. Daniel Plaisted SDET Microsoft Corporation. Windows 8 introduces a new app development platform for Metro style apps. You can use your existing .NET skills to write Windows Metro style apps.

#rake #saw #swage #drill #trowel #auger #bore #burin
Bringing existing managed code into Metro style apps - slide 1
01 / 16Bringing existing managed code into Metro style apps
1 / 17

Télécharger la présentation

Bringing existing managed code into Metro style apps
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. TOOL-790C Bringing existing managed code into Metro style apps Daniel Plaisted SDET Microsoft Corporation

  2. Windows 8 introduces a new app development platform for Metro style apps.

  3. You can use your existing .NET skills to write Windows Metro style apps.

  4. You can move your existing .NET code forward.

  5. demo Windows Phone flash card app

  6. The ViewModel Pattern Presentation logic ViewModel Binding Design w/ XAML View Model XAML Code Data and Business Logic

  7. View to ViewModel Binding ViewModel View • <!– HomeView.xaml--> • <ListBoxItemsSource= • "{BindingLists}"/> • <!-- ListBoxItemTemplate --> • <Image Source="{Binding Image}"/> • <TextBlock Text="{Binding Name}"/> // HomeViewModel.cs publicList<FlashCardListViewModel> Lists{ get; privateset; } // FlashCardListViewModel.cs publicImageSourceImage { get; privateset; } publicstring Name { get; privateset; } View ViewModel

  8. Ways to move your code • Start from scratch • Copy everything • Shared code and conditional compilation • Portable Class Library

  9. Differences we’ll see • UI namespace is different • WinRTvs .NET types • INotifyPropertyChanged • ICommand • Behavioral differences • URIs • Navigation • Platform differences • App startup and lifecycle model • File APIs • Picture chooser

  10. demo Porting a Windows Phone app to Metro style

  11. Differences we saw • UI namespace is different • WinRTvs .NET types • INotifyPropertyChanged • ICommand • Behavioral differences • URIs • Navigation • Platform differences • App startup and lifecycle model • File APIs • Picture chooser

  12. Further Information • [TOOL-515T] Tips and tricks for developing Metro style apps using XAML • [TOOL-531T] Using the Windows Runtime from C# and Visual Basic • [APP-737T] Metro style apps using XAML: what you need to know • [TOOL-810T] Async made simple in Windows 8, with C# and Visual Basic • [TOOL-930C] A .NET developer's view of Windows 8 app development • Documentation: .NET for Metro style apps overview Contact Info: daplaist@microsoft.com Twitter: @dsplaisted

  13. Call to Action Go make great Windows Metro style apps!

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

  15. © 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.