{"id":16045,"date":"2018-01-08T09:00:51","date_gmt":"2018-01-08T17:00:51","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudio\/?p=16045"},"modified":"2018-01-08T09:00:51","modified_gmt":"2018-01-08T17:00:51","slug":"visual-studio-code-java-debugger-adding-step-filter-and-expression-evaluation","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/java\/visual-studio-code-java-debugger-adding-step-filter-and-expression-evaluation\/","title":{"rendered":"Visual Studio Code Java Debugger Adding Step Filter and Expression Evaluation"},"content":{"rendered":"

Happy new year! We\u2019d like to thank you all for using Visual Studio Code for your Java development as well as for sharing your feedback. Within just three months, we\u2019ve published 5 releases for our Debugger for Java<\/a> extension for Visual Studio Code and received 400K+ downloads. With our new 0.5.0 release, we\u2019re adding two new exciting features: Expression Evaluation and Support Step Filters.<\/p>\n

Expression Evaluation<\/h2>\n

The debugger now enables you to evaluate expressions in variable watch window as well as debug console at runtime. So now you can see the value of both the simple variables, single-line expressions, as well as short code fragments within the running context. You can then monitor and validate the change of the value when your code is being executed. See below<\/p>\n

\"VS<\/a><\/p>\n

Support step filter<\/h2>\n

Step filters are commonly used to filter out types that you do not wish to see or step through while debugging. With this feature, you can configure the packages to filter within your launch.json<\/i> so they could be skipped when you step through. See below<\/p>\n

\"VS<\/a><\/p>\n

Other updates<\/h2>\n

This release also includes a few other enhancements:<\/p>\n

    \n
  1. Publish the binaries to the maven central repository<\/li>\n
  2. Adopt new Visual Studio Code 1.19.0 debug activation events<\/li>\n
  3. Improving searching performance by looking up the stack frame’s associated source file from source containers directly instead of leveraging the original jdt search engine<\/li>\n
  4. Bug fixes<\/li>\n<\/ol>\n

    You can find more details in our changelog<\/a>.<\/p>\n

    Try it out<\/h2>\n

    If you\u2019re trying to find a performant editor for your Java project, please give Visual Studio Code a try<\/p>\n