views:

396

answers:

4

When I use the [Debug] button in Gallio, the breakpoints in my unit tests are not hitting. The unit tests are written with MbUnit/Gallio. I am using MbUnit/Gallio version 3.1 build 397 with Visual Studio 2010 Beta 2. The unit tests run to completion in Gallio Icarus, but they run past the breakpoints. I see the symbol tables loading in VS, but it does not stop at the expected breakpoint, so I am unable to debug it.

A: 

Is there anything in the Icarus Runtime log? One problem some people have had is that you can't debug using an instance of Visual Studio running as Administrator from an instance of Icarus that is not.

Jeff Brown
+1  A: 

This is the Icarus Runtime log:

Disabled plugin 'Gallio.VisualStudio.Shell': The plugin enable condition was not satisfied: '${process:DEVENV.EXE} or ${process:VSTESTHOST.EXE} or ${process:QTAGENT.EXE} or ${process:QTAGENT32.EXE} or ${process:QTDCAGENT.EXE} or ${process:QTDCAGENT32.EXE}'. Disabled plugin 'Gallio.VisualStudio.Shell100': The plugin depends on another disabled plugin: 'Gallio.VisualStudio.Shell'. Disabled plugin 'Gallio.VisualStudio.Tip100': The plugin depends on another disabled plugin: 'Gallio.VisualStudio.Shell100'. Host process exited with code: 0

I am running Visual Studio and Gallio Icarus as myself (not Administrator), although I do have local admin rights.

RL
A: 

having the same problem

emmanuel buah
A: 

Normally all my Gallio debugging problems are solved by making the test project Platform Target "x86" rather than "Any CPU".

Igor Zevaka
The Platform Target is grayed out in my Test project. It's currently set to "N/A". Know why VS2010 does not allow me to change this setting to "x86"?
RL
Never seen it being "N/A". For me i's only ever greyed out when I am debugging.
Igor Zevaka