Is there a way to get Visual Studio to modify the solution file after each test run?

Question

Visual Studio seems to occasionally change the list of .vsmdi files in my .sln every time I run unit test. This is annoying because my version control client believes that the .sln file should be checked, even if I don't want to check it. Is there a way to keep Visual Studio from redirecting the .sln file after a test run?

Edit: Find a Microsoft Connect question discussing this that sucks because things just disappear from there after a while and its terrible bug tracker

Answer 1

I do not believe that a solution exists. A good connection case that better documents the problem and the playback problem is this one . At the very end of the page, the commentator offers a workaround that I reproduced here. I did not actually check this workaround for myself, I think I was numb to undo the changes caused by this error :(

From the case of connection:

I was able to reproduce this problem by running Developer A tests with the vsdmi file while checking Developer B for this and adding unit tests to vsdmi. Usually this will result in a new one that needs to be generated.

The workaround that worked for me is to create vsdmi files on dev for units that have not registered with SCC and created a special vsdmis for assembly testing and regression automation.

Yuck, but it works.

Answer 2

Edit: Oh, was confused about the "vsmdi file list". The suggestion would not work.

Answer 3

This is a question for ages ... I always check if a solution has been checked for any reason before I take effect.