Author Topic: [EA17] EA does not evaluate COM objects in JavaScript debugger anymore  (Read 4137 times)

Roman Liebsch

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
In 17 I am not able to debug java scripts and evaluate for instance COM objects like a Msxml2 DOMDocument in the "Locals". They are not shown at all. And if I try a mouse-over on such variables the debugger even stops execution.

In EA 16 it is working perfectly fine.
I might remember in former EA version where you have to install the old Microsoft Script Debugger but I guess Sparxs completely swtiched to JavaScript.

Anyone the same issue or even a solution?

Thanks!
Roman

Roman Liebsch

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: [EA17] EA does not evaluate COM objects in JavaScript debugger anymore
« Reply #1 on: October 24, 2024, 07:03:53 am »
I found a workaround.

If I use the VEA folder from EA 16.1.1628 in the EA17.0.1703 folder then symbols arise again.

BUG is reported to EA now.

ngong

  • EA User
  • **
  • Posts: 273
  • Karma: +1/-2
    • View Profile
Re: [EA17] EA does not evaluate COM objects in JavaScript debugger anymore
« Reply #2 on: October 29, 2024, 06:17:47 am »
Running my JScript in EA17, that worked fine in EA16, led to
...
[42272393]      Agent: Started
[42272423]      Failed to get EA::IDualApp interface [0x80029c4a]
[42272425]      Microsoft Process Debug Manager creation Failed: 0x80040154
[42272425]      This is included as part of various Microsoft products.
[42272425]      Download the Microsoft Script Debugger to install it.
[42272425]      Failed to initialize JScript engine
[42272426]      Debug Session Ended


Could this be the same issue or should I look for a no-longer-supported version of the Microsoft Script Debugger?
Rolf