Error when using a conditional breakpoint on System.Type
⚠ Heads up, seems this is no longer available since Visual Studio 2022.
In my case I was using Visual Studio 2013, NUnit 2.6.4, and attaching a debugger to a unit test session, and I was getting a similar message:
The condition for a breakpoint failed to execute. The condition was 'type.Name.Contains("FooBar")'. The error returned was 'Inspecting the state of an object in the debuggee of type System.Type is not supported in this context.'. Click OK to stop at this breakpoint.
This was caused by a missing feature in the new debug engine Microsoft had introduced, apparently. Following instructions from this msdn blogpost I got things to work. The instructions boil down to:
- From the "Tools" menu open "Options"
- On the left hand side pick "Debugging", "General"
- Scroll all the way down to check "Use Managed Compatibility Mode"
This should switch to the legacy debug engine, which in my case allowed for expressions on Type in break point conditions. Note that you do need to restart your app or debugging session, obviously.
Disclaimer: I have no idea what other effects checking this option had. Personally, I turned it back off when I was done with the task that required it...
You say that Type.FullName == "Malt.Organisation" causes it to break, have you tried this.Type.FullName == "Malt.Organisation"?
Another possibility, does the debugger think you are trying to invoke a static method with having the variable named Type like its class name? Does renaming the Type variable to something else fix it?