ktopanov
Results
1
comments of
ktopanov
I can confirm that the exception is gone for me with that 3.0.2 preview (MS Visual Studio 2017).