Can't initialize with a null SynchronizationContext.Current

[Daniel Chalmers]

If SynchronizationContext.Current is null, VirtualDesktopProvider.Initialize will throw an InvalidOperationException: 'The current SynchronizationContext may not be used as a TaskScheduler.' at

VirtualDesktop/source/VirtualDesktop/VirtualDesktopProvider.cs

Lines 28 to 29 in a6aba70

 public Task Initialize() 
 	=> this.Initialize(TaskScheduler.FromCurrentSynchronizationContext()); 

This stops a blank console app from using VirtualDesktop.

Steps to reproduce:

• Create a new console app
• Target Windows 10 in app.manifest and add a reference to VirtualDesktop 3 beta
• In the main method, call VirtualDesktopProvider.Default.Initialize() (or a method that calls it for you like VirtualDesktop.GetDesktops()).

Workaround:
Call SynchronizationContext.SetSynchronizationContext first or use Initialize(TaskScheduler scheduler).