1. 11/14/ :04 AM
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Desktop Bridge Apps & User Transition
11/14/ :04 AM
P4067
Desktop Bridge Apps & User Transition
Arian Ghotbi
Senior Program Manager
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Overview: Desktop Bridge
Simplified and trusted deployment
Clean and simple install/uninstall
Updates delivered using differential packages
No elevation/UAC
Greater reach, easier monetization
Windows Store reaches 400+ million users today
Monetize using local payment methods
Windows Store for Business for business customers
Modernizing with UWP
Add UWP capabilities (Live Tiles, push notifications, in-app purchase)
Add XAML UI, move away from monolithic solutions and migrate at your own pace

4. Problem
Previous desktop app and the packaged app can co-exist on the same machine leading to user confusion

5. Consider
How to provide the best user experience when transitioning from the previous desktop app to the packaged version

6. Outline Transition taskbar pins and start tiles via the manifest
Transition file type associations and protocol handlers via the manifest
Migrate previous user data on first launch
Uninstall previous version on first launch

7. Pins & Tiles Transition [MANIFEST]
You can provide the shortcut path to your .lnk file the transition to happen Below is sample XML code which is declared under the application element
<rescap3:Extension Category="windows.desktopAppMigration">
<rescap3:DesktopAppMigration>
<rescap3:DesktopApp ShortcutPath="%USERPROFILE%\Desktop\[my_app].lnk" />
<rescap3:DesktopApp ShortcutPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\[my_app].lnk" />
<rescap3:DesktopApp ShortcutPath="%PROGRAMDATA%\Microsoft\Windows\Start Menu\Programs\[my_app_folder]\[my_app].lnk"/>
</rescap3:DesktopAppMigration>
</rescap3:Extension>
Take out AUMID

8. File Type Association & Protocol Handler Transition [MANIFEST]
You can also migrate the FTA & protocols associated with the previous app by providing the ProgId to migrate from The XML snippet below is declare under a FileTypeAssociation extension
<uap:Extension Category="windows.fileTypeAssociation">
<uap3:FileTypeAssociation Name=“.foo”>
<rescap3:MigrationProgIds>
<rescap3:MigrationProgId>[My_App_ProgId]</rescap3:MigrationProgId>
</rescap3:MigrationProgIds> …
What’s ProgID?
How do you find yours?
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.ftj\UserChoice
You can visit this MSDN page to find out the ProgID for your app

9. User Data Migration User data is app-specific Best practice:
Upon first launch of your app, look for old user data and migrate
You should attempt to migrate prior to uninstallation to avoid data loss.
You should also build UX to help end-users understand what’s happening (i.e. ‘We are attempting to import your previous data…’)
You should *move* old data as opposed to ‘copy’.

10. Uninstallation of previous desktop app
Best practice:
Create a new prompt, explaining to the user:
What is about to happen
Why it is recommended
What’s going to happen to their old data (or already happened)
Launch the UninstallString to offer the uninstall experience
You should know what your Win32 app’s uninstall string looks like and/or where it is located in the registry
User may choose to decline:
App needs to make a decision to block or allow side-by-side
Where is the UninstallString typically registered in RegEdit?
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{7AD02FB8-B85E-44BC-8998-F4803BA5A0E3}
MsiExec.exe /I{7AD02FB8-B85E-44BC-8998-F4803BA5A0E3}

11. Summary Transition from the desktop app Call to action
Taskbar pin and start tile transition
Filetype Association and Protocol Handler transition
User data migration on launch
Uninstallation of the previous version
Call to action
Visit the blog post for code samples and detailed guidelines:

12. 11/14/ :04 AM
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.