wasm][debugger] Refactor evaluateOnCallFrame

[ilonatommy]

Currently: we have 2 functions handling on-frame-evaluation:

• Resolve, targeting simple expressions that can be resolved talking to the runtime (e.g. local variables, object members, static classes etc)
• CompileAndRunTheExpression, targeting more complex expressions using Roslyn. It is triggered only when Resolve fails in evaluating the expression.

Goal:
merge these two processes because some expressions require both sources of information, it could help solving these issues: #66823, #67029, #66824.

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Currently: we have 2 functions handling on-frame-evaluation:

• Resolve, targeting simple expressions that can be resolved talking to the runtime (e.g. local variables, object members, static classes etc)
• CompileAndRunTheExpression, targeting more complex expressions using Roslyn. It is triggered only when Resolve fails in evaluating the expression.

Goal:
merge these two processes because some expressions require both sources of information, it could help solving these issues: #66823, #67029, #66824.

Author:	ilonatommy
Assignees:	ilonatommy
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-

[lewing]

@ilonatommy what is the status of this?

[ilonatommy]

Not started. It's not of a high priority, so let me move it to the future.

[ilonatommy]

Connected issues got solved without refactoring. Closing as not needed right now.