Clever Geek Handbook

Why does Visual Studio 2005 take so long to update my VSMDI file?

I am using the solution with many projects in Visual Studio 2005. Unfortunately we are using testing tools. My problem is that many times when I open Test Manager by double clicking the VSMDI file to do some testing, I get an hourglass of at least 10 minutes while the horrible Microsoft code God knows I thinking trying to find new tests? Does anyone have a workaround for this?

Thank!

0


source to share


1 answer


I know this is an old question now, but I'm already used to using MSTEST. Here are my recommendations for effective use in a large solution:



  • Use the shortcuts CTRL-R, T (or CTRL-T for debugging) to run tests in the current context (e.g. namespace, class, method). This fits well enough for the TDD approach.
  • Don't use Test View, Test Lists, or Test Runs tags if you can avoid it.
  • Typically, I find myself having problems with the VSMDI file when switching between different build configurations. VS thinks for a while and then asks me to check the VSMDI file (and I just canceled the checkout dialog).
0


source






More articles:


All Articles