*.vsmdi files

I don't know if this will help but I'll give it a try...

Make sure the vsmdi file is checked in, look into the pending changes window.

My understanding of this vsmid file is that you can link this file when creating a build.

When you create a build, you can create custom targets. In that custom target, you can tell your build to go an execute a particular test(unit test for example), all that's left to do is write inside the target, to go execute this vsmdi file.

Again, this might not answer your question but it might clarify it...

If I'm wrong about this, because I haven't tried this and I'm only assuming, then disregard this post :)

Hope this helps!
Sincerely

Vince

Hi, Winnie Ng,

Here answers on Your questions:
"When the .vsmdi file was first created for you, did you check it in as part of the solution into SourceSafe?"

> Yes, The .vsmdi file was checked as part of the solution to SourceSafe.

"And when you did, did you happen to have move the file, or was it in its originally created location (on disk it should be at the location where the .sln file is)"

> No. The file is in the same directory as .sln file.

"At what point did a new .vsmdi file gets created -- was it when you executed a certain command in VS?"

> I just tryied to recreate it with creating new list of test, new test class and adding of a new test to old class.
> But nothing can spoile the .vsmdi file. Unbelivable! I even can run debug today! (Previously I wrote that I had problem to run debug of a test).

"Also, have you tried removing the newly created file from the solution, and do an "Add Existing item" to add back the old file?"

Yes, I did. But then when I add new test class, new .vsmdi were created.

The last thing that I did was uncheckout of solution and .vsmdi files (with losing of tests). But now it works.

Boris.