AV: Using VIXCOM API against both VMWare workstation and VI server in the same process
It seems that VIXCOM dies when trying to connect to a Workstation after working with a VI connection, and vice-versa. The call to Connect hangs and there's an access violation on another thread. This sounds like a rare use scenario, but I think this hides a real problem in the VIXCOM API implementation. For me, the problem is in unit tests for VMWareTasks since the library works with both Workstation and VI.