This article has been archived. It is offered "as is" and will no longer be updated.
Source: Microsoft Support
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
You have Team Foundation Server 2008 or 2005. Your VSMDI file is added to your solution and under source control. Various users unit test the solution.
The VSMDI file is automatically checked out and a new vsmdi file is created using the naming convention MySolutionName1.vsmdi, MySolutionName2.vsmdi, MySolutionName3.vsmdi and
Someone ran a test while someone else was modifying the vsmdi file. Team Test detects that the VSMDI file is out of sync;therefore, Team Test it makes one and thus you see the incrementing vsmdi files.
Going forward you want to make sure the file is not marked for auto checkout when it is modified. When the current tester has the VSMDI file checked out you, do not want other users to be able to check it out. You want your developers to checkout the file, run a test, and check it back in.
Here are the steps to fix the problem:
1. Backup your local copy of the application to some other place (directory). 2. Delete the local copy of application where your workspace is mapped. 3. Delete the vsmdi file from source control then do a check in on the vsmdi file. Checking it in will actually delete it from source control. 4. Perform a Get latest from source control. 5. Open the solution and check that you don't have vsmdi file. The vsmdi file should not be in source control or in the solution. 6. Modify test and it will generate a new vsmdi file. 7. Check in the vsmdi file and mark it to prevent auto checkout when it is modified:
Select the VSMDI file and right click.
Choose Check Out for Edit.
Choose the "Check out- Prevent other users from checking in and checking out" option.
Press Check out. Button.
8. Run another test and to generate a new vsmdi file. 9. Check out the vsmdi file. 10. Modify the test and see if it generates a new file. 11. Go to the other machines (other developers) and delete local copy of the vsmdi file.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.