Closed KarolAntczak closed 7 years ago
Steps to reproduce:
OK, it is caused by Visual Studio, not by the extension itself. Reseting Experimental instance seems to solve the problem, as explained here.
Steps to reproduce: