ExtendScript Debugger for Visual Studio Code (Windows-Compatible Prerelease)

Erin Finnegan
Feb 13 · 2 min read
An ExtendScript Debug Session in progress

Common issues to avoid

Many early users attempted to run the ExtendScript Toolkit desktop app and the VSCode plugin simultaneously; this does not work, they both rely on the same BridgeTalk message queue. Be sure to quit ExtendScript Toolkit before launching the VSCode plugin.

Bug fixes

Here are some of the bugs we fixed, many of which were based on your discussions in the prerelease forum:

  • UXP-7458: Adding support for “dontBreakOnErrors” and “debugLevel” setting through config file.
  • UXP-7532: Printing runtime error text to output channel of VSCode.
  • UXP-7608: Added support for start without debugging.
  • UXP-7607: If the user tries to start multiple debug session then the dialogue “A Debug Session is already running. Please close it before starting a new session.” will appear.
  • UXP-7535: Added support for custom engines.

Join the prerelease and try it out today

If you happen to be joining the prerelease for the first time, please keep in mind that the program requires a prerelease agreement, which is the equivalent to an NDA (non-disclosure agreement). Please don’t share prerelease builds or other information outside of the prerelease forums.

Adobe Tech Blog

News, updates, and thoughts related to Adobe, developers, and technology.

Erin Finnegan

Written by

Community Engineer at Adobe. Views are my own.

Adobe Tech Blog

News, updates, and thoughts related to Adobe, developers, and technology.