views:

323

answers:

2

When I try to run unit tests, in debug mode only, on "Microsoft Visual Studio Team System 2008 SP1" and the Test Results view is open in a screen other than the main one (I have 2 monitors), the devenv.exe process crashes. Have you ever encountered a similar error? Have you found a workaround for it?

+2  A: 

I have not heard of that issue before. It would be great if you could file a bug with Visual Studio Connect on the issue.

Customer bugs, especially easily reproducible ones, are taken very seriously and it will be looked at.

Also would you mind posting back in the comments what the ID of the bug is?

JaredPar
The bug ID is 463445
Jader Dias
A: 

Resolved for my scenario: it was a reference issue. With Fusion assembly bind logging fully turned on, I found (having recently moved, again, from x86 to x64) that libraries I was referencing in a web.config were strong-named when compiled for x86, but when I recompiled them for Any CPU or x64, I hadn't used strong naming and therefore had a null PublicKeyToken. So assemblies that were in fact deployed, weren't being found by name by the framework at runtime.

Bad references/assembly bind issues/config file issues seem to be a real sticking point around .NET -- lots of potential for crashing and burning with little or no direct feedback, little or nothing useful ending up in the Event Log.

andrewbadera