Step #3 Doesn't Work - Instructions Update Required

[LanceMcCarthy]

After RS4 (SDK 16299), the breakpoint in the RuntimeComponent will not be hit. This is a known regression.

There is a workaround available, I will step through these in details in a follow up reply below.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3a1bd8a3-fcbd-16cf-e549-e23e628a07b5
• Version Independent ID: 7436c663-bc96-51bc-11a8-d0c11ad5d8cf
• Content: Run a background task when your UWP app is updated - Windows UWP applications
• Content Source: windows-apps-src/launch-resume/run-a-background-task-during-updatetask.md
• Product: uwp
• Technology: processes-and-threading
• GitHub Login: @lastnameholiu
• Microsoft Alias: alholiu

[LanceMcCarthy]

Workaround

1. In the UpdateTask class, add a conditional compilation block for DEBUG.
2. Programmatically invoke the Debugger using Debugger.Launch()

public sealed class UpdateTask : IBackgroundTask
{
    public void Run(IBackgroundTaskInstance taskInstance)
    {
        var deferral = taskInstance.GetDeferral();

#if DEBUG
        // Manually trigger Just In Time debugger
        System.Diagnostics.Debugger.Launch();
#endif

        // Your code here

        // Done with task
        deferral.Complete();
    }
}

At runtime, a Just-In-Time Debugger dialog window will open, allowing you to select a Visual Studio instance to debug with:

After choosing a Visual Studio instance, the Launch line will be the initial entry point for the debugger, as if you placed a breakpoint there:

[hkhmsft]

Hi @LanceMcCarthy , thanks so much for submitting that thorough workaround. Appreciate you pointing this out. I'll pursue this suggestion and add in a work item to get it fixed. Look back for this thread for updates in the future once this is completed.