The latest version of "Chutzpah Test Adapter for the Test Explorer" (v 3.2.2) triggers multiple "Object reference not set to an instance of an object." popups when **opening** and **reloading** certain solutions / projects.
I have Visual Studio 2013 with Update 3 installed.
Tests still appear to be detected and run just fine - it's just very irritating having to close all the popups. :-)
Comments: Thanks for looking into this. Hopefully it will be resolved soon. I've had to disable Chutzpah because the 7 dialogs appear so often that I can't get any work done and would really like to go back to using Chutzpah... I have a lot of add-ins that enumerate files in my solution and Chutzpah seems to be the only one with the issue. While it still happens with one instance, it seems much more prevalent when I have multiple instances open and save a config file or something. Is it possible that Chutzpah is just grabbing a running instance of devenv.exe rather than the current instance? Just throwing that out there since I had another add-in that did that. I'm guessing it's not the case here since it'll happen with one instance, but as I said, it seemed to be more prevalent with multiple instances.
I have Visual Studio 2013 with Update 3 installed.
Tests still appear to be detected and run just fine - it's just very irritating having to close all the popups. :-)
Comments: Thanks for looking into this. Hopefully it will be resolved soon. I've had to disable Chutzpah because the 7 dialogs appear so often that I can't get any work done and would really like to go back to using Chutzpah... I have a lot of add-ins that enumerate files in my solution and Chutzpah seems to be the only one with the issue. While it still happens with one instance, it seems much more prevalent when I have multiple instances open and save a config file or something. Is it possible that Chutzpah is just grabbing a running instance of devenv.exe rather than the current instance? Just throwing that out there since I had another add-in that did that. I'm guessing it's not the case here since it'll happen with one instance, but as I said, it seemed to be more prevalent with multiple instances.