In this section

A feature-by-feature guide to the high-level differences you should be aware of when migrating the code and the XAML from your original WPF or Silverlight app. Includes guidance on redesigning your UI, migrating to a new app model, and so on.

Developer audience

The info throughout this section is intended for developers who have created WPF or Silverlight apps, and who want to create similar Windows Store apps.

A WPF app or a Silverlight app can be written in C# or Microsoft Visual Basic for code, and XAML for UI definitions. Windows Store apps can be created using these same code languages and XAML for UI. The shared languages provide a substantial head start towards creating a similar app as a Windows Store app.

Note A WPF app can also be written using C++/CLI, but that programming model doesn't use XAML for the UI. It's possible to migrate code from C++/CLI to Visual C++ component extensions (C++/CX) as supported in a Windows Store app, but guidance for this migration path is not included here.

Here are some other resources that can help you find the Windows Store app documentation for specific feature areas or tasks: