We have informed Microsoft about this issue being present in VS2013 as well. Hopefully, they will include a fix for it in a next update/release. If/when we hear back from them, we will update this thread.
Posted on:13 Jul 2016 18:21
This is also an issue in Visual Studio 2013. I just checked the patch that Microsoft did to 2013 mentioned here:
This patch did resolve our ui mapping issues in 2013, but it still has the Access Violation exception thrown when you try to access a standard .net control or try to send keystrokes using the .net keyboard class. This is the same behavior we see in VS2015.
Posted on:02 Jun 2016 06:50
We have investigated this case and it appears to be an issue with Microsoft implementation of CodedUI. After discussion with them, we were assured that a fix will be introduced with the next update of Visual Studio 2015, probably Update 4 and/or the next Visual Studio version.
Once either of these is introduced, this should be resolved.