Thanks.

One suggestion: in ObjectExtension.cs => GetInstanceProviders(…) method. It would be good to add the checking for obvious types that cannot be instantiated? E.g using Type.IsInterface or Type.IsAbstract methods. It saves unnecessary exception being thrown. Also, some people use exception debugging in VS which throw all exception, this will generate unnecessary false alarm

I am emailing you to ask about the error list.

If the error list is closed or auto-hidden when the continuous test runs automatically; I do not see the failed test. Is there a way to fix this?

Steps to reproduce. 1. Create a simple test “Assert.IsTrue(false);” 2. From the menu, view / errorlist to ensure the error list is showing. Ensure it is not auto-hiding. 3. Build and then view the error of the test failing. 4. Now close or auto-hide the error list. 5. Build and note that the error list does not show.

thanks

To test your installation, simply build a solution containing a failing test and watch it appear in the error list.

Not sure how to provide a sample for that… since the plugin isn’t even loading.

I’m using default installs of both VS on a 64 bit windows 7

int chunkSize = Math.Min(blockSize, data.Length – chunkPosition );

instead of

int chunkSize = Math.Min(blockSize, data.Length – (chunkPosition * blockSize));