Windows 10: Visual Studio Code- how do I debug a loaded module?

Julian Milano · Nov 13, 2024

In Powershell ISE, I was able to open a function code module in the ISE, set a breakpoint, in the command line window below, dot source the function code, then run the function from the ISE command line with parameters and was able to debug the function.I tried the same thing in VSC however it does not recognise the breakpoint when the function is run from the Terminal window. Is this possible?My source for the module is this: https://knowledge.broadcom.com/external/article?articleNumber=370419For some strange reason when I try with the Broadcom supplied module, my ISE crashes to the desktop,

:)

Brink · Nov 13, 2024

Supporting JUnit 5 in Visual Studio Code

After supporting the widely adopted JUnit 4 with the Java Test Runner extension for Visual Studio Code, we’ve received suggestions to add additional test frameworks, like JUnit 5 and TestNG. We’ve added initial support for JUnit 5, including running, debugging test cases as well as test report. Please give us a try and let us know your feedback.

Expression Evaluation based Conditional Break Point

After introducing expression evaluation in our January release for the Java debugger extension, we are bringing the functionality to conditional break points. Now, you can set your breakpoint to break when an expression evaluates to true. We believe this could be a very useful feature when debugging your Java application using Visual Studio Code.

Other Updates

We’ve also added new features to our Java on Visual Studio Code extension lineup, including:

Java Test Runner

Trigger tests from test explorer on different levels

Add command to open log file

Add setting to specify the position of test report

Tomcat

Add several context commands in Tomcat Explorer

Add support for JVM customization and Tomcat server configuration

Add command palette entries for user input

Maven

Add support for auto-update maven project explorer when pom.xml is updated

Try it out

Please don’t hesitate to try Visual Studio Code for your Java development, and let us know your thoughts! Install the Java Extension Pack which includes Language Support for Java by Red Hat, Debugger for Java, Maven, and the Java Test Runner.

Additional resources

If you’re working on Spring Boot, there are also extensions for Spring Boot Tools and Spring Initializr we’ve developed in partnership with Pivotal.

Learn more about Java on Visual Studio Code.

Explore our step by step Java Tutorials on Visual Studio Code.

Xiaokai He,
Program Manager
Click to expand...

Source: Supporting JUnit 5 in Visual Studio Code | The Visual Studio Blog

Brink · Nov 13, 2024

Emmet 2.0 in Visual Studio Code

August 7, 2017 Ramya Rao, @ramyanexus

In the July 2017 release of Visual Studio Code (version 1.15), we're shipping a better Emmet experience which has been in preview for the past 2 releases.

It's features include:

Emmet abbreviation expansions in suggestion/auto-completion lists.

Multi-cursor support for most Emmet actions.

Updated support for custom Emmet snippets.

As part of this update, we have re-written all of the Emmet actions using new npm modules from @emmetio.

An important change is that the Tab key is no longer the dedicated keyboard shortcut for expanding Emmet abbreviations. Instead, Emmet abbreviations will now appear in the suggestion list. They can be selected like any other smart completion and on selection, the abbreviation will be expanded.

This may take some getting used to but we think you'll see the benefits of Emmet abbreviations being treated as suggestions or smart completions. You can still bind any keyboard shortcut (other than Tabkey) to the editor.action.emmet.expandAbbreviation command or use Emmet: Expand Abbreviation from the Command Palette.

Read on to learn about the Emmet 2.0 changes in Visual Studio Code.
Click to expand...

Read more: Emmet 2.0 in Visual Studio Code

Brink · Nov 13, 2024

Adding support for Debug Adapters to Visual Studio IDE

Since its release, Visual Studio Code’s extension model, based on well-known web technologies such as TypeScript and JSON, has attracted a great deal of participation from the community, with hundreds of extensions published to provide support for exciting new languages and technologies. Visual Studio 2017 took the first steps towards participating in this ecosystem in November, with the release of the Language Server Protocol preview. Now, in Visual Studio 2017 version 15.6, we’re excited to announce support for another Visual Studio Code extension component – the debug adapter. If you’ve previously written a debugging extension for Visual Studio Code, you can now use it in Visual Studio as well, generally with only minor modifications. If you’re considering implementing debugging support for a language or runtime, doing so via a debug adapter will allow you to reach both Visual Studio and Visual Studio Code customers without having to support two separate codebases.

What is a Debug Adapter?

A debug adapter is a program that can communicate with a debugger UI using the Debug Adapter Protocol. An adapter can act as a bridge between the UI and a separate debugger (such as GDB or LLDB), or can be a debugger in and of itself (such as “vsdbg”, which supports CoreCLR debugging on Linux and macOS). The Debug Adapter Protocol is JSON-based, and libraries for working with it are available in many languages, including Node.JS and C#/VB.Net.

How do I get started?

You will need to have Visual Studio 2017 version 15.6 installed.

Samples and documentation for the Visual Studio Debug Adapter Host are available on GitHub: GitHub - Microsoft/VSDebugAdapterHost: Visual Studio Debug Adapter Host.

On the Debug Adapter Host wiki, you’ll find walkthroughs that demonstrate testing and packaging a debug adapter for use in Visual Studio. After following the walkthrough, you’ll be able to debug with Visual Studio Code’s “Mock Debug” adapter in Visual Studio:

The wiki also contains documentation on new functionality added to the Debug Adapter Protocol to support Visual Studio scenarios, such as the ability to edit values in the “Watch” window, control the formatting of data and stack traces, and more.

If your extension also contains a Language Server, you may also be interested in the preview release of Visual Studio’s Language Server Protocol support.

How do I provide feedback?

You can provide feedback by filing issues on GitHub, or you can email the team directly at L: [email protected].

Andrew Crawley,
Sr. Software Engineer, Visual Studio
Click to expand...

Source: Adding support for Debug Adapters to Visual Studio IDE | The Visual Studio Blog

Windows 10: Visual Studio Code- how do I debug a loaded module?

Visual Studio Code- how do I debug a loaded module?

Visual Studio Code- how do I debug a loaded module?

Visual Studio Code- how do I debug a loaded module?

Visual Studio Code- how do I debug a loaded module? - Similar Threads - Visual Studio Code

Visual Studio Unable to start debugging

Visual Studio Code- how do I debug a loaded module?

Not able to debug c++ code on visual studio 2022

Not able to debug c++ code on visual studio 2022

Start Debugging Problem Visual Studio!!!

Start Debugging Problem Visual Studio!!!

Start Debugging Problem Visual Studio!!!

Visual Studio Code

visual studio code