avivanoff

Works just fine for **build** and **rebuild** targets.

Would be nice to have per-user launch settings that does not need to be committed.

More than 4.5 years? Really?

Add .testsettings file to MSTest V1 project.

This is what I found in DesktopTestContextImplementation.cs, line 171: // In MSTest, it is actually "In\697105f7-004f-42e8-bccf-eb024870d3e9\User1", but // we are setting it to "In" only because MSTest does not create...

Do not use .testsettings as a deployment item. Select them as Test Settings in Visual Studio when running tests, or as /Settings argument to vstest.console.exe.

Sample project. [UnitTest2.zip](https://github.com/Microsoft/testfx/files/2515120/UnitTest2.zip)

A lot of our tests rely on TestContext.TestResultsDirectory being unique to provide test isolation. And because most of our tests run in parallel, if TestContext.TestResultsDirectory is not unique, we have...

The behavior between V1 and V2 changed. You should at least document it. And thank you for all that extra work we now have to do.

We have a custom zip-based containers (king of what NuGet packages are) and are using signtool.exe to create signatures.