debugging - Evaluating expressions using Visual Studio 2005 SDK rather than automation's Debugger::GetExpression -


"postprint" itemprop = "text">

I'm looking into an add-write (or, if necessary, package) Visual Studio 2005 that has the clock window type functionality Evaluation of expression and type of exam - - for the needs of exams. Automation facilities provided by debugger :: GetExpression , which is quite useful, but the information provided is a bit crude.

From looking through the docs, it seems like a IDebugExpressionContext2 would be more useful, in this form if I can get more information from one expression I think - without thinking about type and any member and so on and all the more detailed information about coming in through the form of stars.

I can actually do a IDebugExpressionContext2 < / Code> is not discovered in any way Yes, though! Feeling relevant to IDebugProgramProvider2 , in that I can start slowly with IDebugProgramProvider2 :: GetProviderProcessData and then supply something like this my expression reference Until reaching inside - but I am required to supply a port on it, and it is not clear to recover the port corresponding to the current debug session. (Even if I tried every port, it is not clear what port is right ...)

I suspect that this is not just a supported use case But any luck I have not just left off some crashingly clear.

Can anyone help? After using itemprop = "text">

IDebugExpressionContext you ultamitely IDebugProperty

An example of getting ahold will be reached. This interface has been implemented by the Expression Evaluator service. This is usually a language specific service. This is designed to exclude language specific details of expression evaluation. It considers very high level orders as "evaluation" and inspection.

I do not think you are going to get whatever you are looking for, because you can not get any kind of object in this way. Almost all the inspection methods return their results in the string form, for example you will not type int32 but instead of string "int" instead it inspects the type of impossible .

I do not believe that what you are trying to do is a supported case. The evaluation of this type of system is not present in the present process. It is present in the debugging process and it is very difficult to gain access to it.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -