Our test project used to work but we broke something - now we get "Couldn't get Configuration" - not much point putting that one into google!
A new solution and test project is fine but we'd like to fix our existing (fairly detailed) solution rather than rebuild it from scratch (and maybe have it happen again)
Any ideas on this one would be great
cheers
Dave
Also the new (working) test project and solution has a .vsmdi file at the solution level which is a test manager config by the looks.
Our broken solution doesn't have one - and 'add new item' doesn't offer that type. Could that be it I wonder?
thanks
Dave
You can create a new VSMDI by going to testview, right clicking and selecting "Open Test Manager", or Test Menu/Windows/Test Manager.
Within test manager, create a new test list -- this should create the VSMDI.
However, this should not cause the issue you are experiencing.
Do you have a .testrunconfig file in your solution? If not, Right click on "Solution Items" under the the solution, and select Add New Item, then "Test Run Configuration", and then Ok. Once this has been added, go to the test Menu, and then "Select Active Run Configuration", and then select which ever appears in there.
Let me know how it goes.
I used Test Menu/Windows/Test Manager but got a dialog with "Exception throw by target of invocation"
Anyway, on to .testrunconfig:
The solution has one and if I choose "Select Active Run Configuration" then I get "Couldn't get Configuration"
When I tried to edit the test run configuration it gave me a "Package load failure - Package 'LoadTestPackage' has failed to load properly " plus a guid etc etc
cheers
Dave
The "Open Test Manager" Item is in Test View, not solution explorer.
I think that my solution is probably beyond repair.. I'm rebuilding it since my reputation as office "unit testing bore" is in danger. I wondered whether it was a VSbeta problem that someone's seen before or just something here.
We've not seen a "Couldn't get configuration" error before, hence why I'm keen to get to the root cause :)
If you do find that just a new solution (not projects) fixes the issue, I'd be grateful if you could send me the two .sln files for me to compare.
I am wondering if your solution happens to consist of one or more setup projects? If so, there is a known problem with beta2 that will cause at least one of the errors you are seeing. If your solution does contain one or more setup projects, is it possible for you to remove them and try again?
Thanks.
Winnie
