Closed Sureshgoudb closed 3 years ago
What version of .Net were you using when you encountered this? I am seeing similar issues on .Net Core 2.1 and am wondering if targeting the .Net framework (4.6.1 or something similar) would fix it.
Fixed in today's v.1.2.2. release.