visual studio code debug adapter executable not found

Make sure that the Configuration field at the top of the window is set to Debug.įor. Specify a calling app in a managed DLL project You want the first profile in launchSettings.json to match the name of the Class Library, and you want it listed first in the file. Rename the new profile to the same name as the default profile.Īlternatively, you can manually edit launchSettings.json to get the same result. In the Launch Profiles dialog box, note the name of the default profile, then select it and delete it. In the new profile, under Executable, browse to the location of the executable (. In the Launch Profiles dialog box, select the Create a new profile icon, and choose Executable. In the Debug tab, select Open Debug launch profiles UI. Select the Properties icon, press Alt+ Enter, or right-click and choose Properties. Select the C# or Visual Basic DLL project in Solution Explorer. Specify a calling app in a C# DLL project (.NET Core. exe file.Īdd any necessary program arguments to the Command Arguments box. In the Command or Remote Command box, add the fully qualified path and filename of the calling app, such as an. In the Debugger to launch list, choose either Local Windows Debugger or Remote Windows Debugger. Select Configuration Properties > Debugging. In the Property Pages dialog box, make sure the Configuration field at the top of the window is set to Debug. Select the C++ DLL project in Solution Explorer. Specify a calling app in a native DLL project Native and managed DLL projects have different settings to specify calling apps. For more information, see How to: Debug in mixed mode. If your managed app calls a native DLL, or your native app calls a managed DLL, you can debug both the DLL and the calling app. For other methods of debugging DLLs, see Debugging DLL projects.

If the app finds and loads a different version of the DLL, that version won't contain your breakpoints. For this method to work, the app must call the same DLL in the same location as the one you configure. Then you can start debugging from the DLL project itself. One way to debug a DLL project is to specify the calling app in the DLL project properties.

Applies to: Visual Studio Visual Studio for Mac Visual Studio Code

Visual studio code debug adapter executable not found