Conversely, for regular UWP apps, you would have only one Executable and one startupTask Extension.ДЇor both Desktop Bridge apps and regular UWP apps, the user is always in control, and can change the Enabled state of your startup app at any time via the Startup tab in Task Manager:ДЄlso for both app types, the app must be launched at least once before the user can change the Disabled/Enabled state.

For Desktop Bridge apps, multiple startupTask Extensions are permitted, each one can use a different Executable.

Conversely, for regular UWP apps this attribute is ignored, and the feature is implicitly set to вЂњdisabled.вЂќ Instead, the user must first launch the app, and the app must request to be enabled for startup activation.

Desktop Bridge apps can set the Enabled attribute to true, which means that the app will start at startup without the user having to manually enable it.

The Desktop Bridge EntryPoint must be вЂњWindows.FullTrustApplication,вЂќ whereas for regular UWP it is the fully-qualified namespace name of your App class.

The new UWP implementation is designed for use generally on UWP, so it uses a general UAP namespace (contract version 5) вЂ“ although to be clear, it is currently still only actually available on Desktop.

Desktop Bridge is only available on Desktop, so it uses a Desktop-specific XML namespace.

The same Extension declaration is used for both Desktop Bridge and regular UWP apps вЂ“ but there are some differences.

The first thing to note is that you must use the windows.startupTask Extension in your app manifest under the Extensions node, which is a child of the Application node.

Open sign in window