This can be set up by creating a new configuration as seen below. Visual Studio Code needs a “debug” configuration in your project’s launch.json file. View and interact with the debug console (expression evaluation)Ī few things didn’t make it into this release:.Access debugging commands (continue, step into, step over, step out, stop restart).Inspect variables (local and global scope, modify variables).Set up breakpoints (hit counts, expressions, debugger statements).
Launch ExtendScript-enabled Adobe applications. We wanted to ensure that it is still possible for you to debug your scripts, even as modern operating systems drop support for 32-bit applications. We weren’t able to implement every single feature of the ExtendScript Toolkit (ESTK), but as we mentioned in our first announcement about the ExtendScript Debugger, we targeted mission-critical debugging functionality for this release. If you participated in the prerelease program, you should uninstall the prerelease plugin before installing the public plugin from the marketplace. Adobe disclaims all warranties, express or implied, including the implied warranties of non-infringement, merchantability, and fitness for a particular purpose. The Windows version of this plugin should be considered a “beta,” and is provided as-is. You can install it from Visual Studio Code by navigating to the Extensions sidebar (Shift + Cmd + X on macOS or Shift + Ctrl + X on Windows) and then searching for “ExtendScript Debugger.” If you have Visual Studio Code 1.31.1, you won’t have to even reload VS Code in order to use the plugin! Important notes before you start We’re excited to announce that the plugin for Visual Studio Code is now live in the Visual Studio Code Marketplace! 
Only a few short weeks ago we released the very first prerelease for the ExtendScript Debugger for Visual Studio Code.
0 kommentar(er)
