TryAttachProcessExitedEventHandler blocks (never returns) while inside the VS debugger

[BobbyCannon]

I'm submitting a...

Bug report (I searched for similar issues and did not find one)

Current behavior

Inside the TryAttachProcessExitedEventHandler method the WebView1?.Process is blocking and never letting the handler to complete. I think it's also the reason why WebView is not rendering while debugging.

Expected behavior

TryAttachProcessExitedEventHandler should complete.

Minimal reproduction of the problem with instructions

Open the Microsoft.Toolkit.Sample.Wpf.WebView project in Visual Studio and debug it using F5

Environment

Nuget Package(s): 
Microsoft.Toolkit.Wpf.UI.Controls
Microsoft.Toolkit.Wpf.UI.Controls.WebView

Package Version(s): 
5.0.0-preview.gb86cb1c4cb

Windows 10 Build Number:
- [ ] Creators Update (15063)
- [ ] Fall Creators Update (16299)
- [X ] April 2018 Update (17134)
- [ ] Insider Build (build number: )

App min and target version:
- [ ] Creators Update (15063)
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] Insider Build (xxxxx)

Device form factor:
- [X ] Desktop
- [ ] Mobile
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT

Visual Studio 
- [X ] 2017 (version: )
- [ ] 2017 Preview (version: )

[BobbyCannon]

Turns out if you comment out the method content it still does not load and work. I assume the WebView control cannot completely initialize while running in the debugger.

[BobbyCannon]

Even "Start without Debugger" (ctrl+F5) also does not allow the control to initialize.

[rjmurillo]

Are you building a debug version yourself or using the packaged version?

[rjmurillo]

@joshholmes FYI