IVsDebugger4.LaunchDebugTargets4 Method

Launches the specified debug targets.

Namespace:  Microsoft.VisualStudio.Shell.Interop
Assembly:  Microsoft.VisualStudio.Shell.Interop.11.0 (in Microsoft.VisualStudio.Shell.Interop.11.0.dll)

Syntax

'Declaration
Sub LaunchDebugTargets4 ( _
    DebugTargetCount As UInteger, _
    pDebugTargets As VsDebugTargetInfo4(), _
    <OutAttribute> pLaunchResults As VsDebugTargetProcessInfo() _
)
void LaunchDebugTargets4(
    uint DebugTargetCount,
    VsDebugTargetInfo4[] pDebugTargets,
    VsDebugTargetProcessInfo[] pLaunchResults
)
void LaunchDebugTargets4(
    [InAttribute] unsigned int DebugTargetCount, 
    [InAttribute] array<VsDebugTargetInfo4>^ pDebugTargets, 
    [OutAttribute] array<VsDebugTargetProcessInfo>^ pLaunchResults
)
abstract LaunchDebugTargets4 : 
        DebugTargetCount:uint32 * 
        pDebugTargets:VsDebugTargetInfo4[] * 
        pLaunchResults:VsDebugTargetProcessInfo[] byref -> unit
function LaunchDebugTargets4(
    DebugTargetCount : uint, 
    pDebugTargets : VsDebugTargetInfo4[], 
    pLaunchResults : VsDebugTargetProcessInfo[]
)

Parameters

  • DebugTargetCount
    Type: UInt32

    [in] Number of debug targets.

  • pLaunchResults
    Type: array<Microsoft.VisualStudio.Shell.Interop.VsDebugTargetProcessInfo[]

    [out, size_is(DebugTargetCount)] List of process identifiers (PIDs) and creation times for the debug targets. PIDs are only returned when DLO_CreateProcess/DLO_Custom and DLO_LaunchBrowser are specified when a new browser process is started (non-attach case).

Remarks

This method extends LaunchDebugTargets3 by adding support for launching Windows Store apps, Windows Phone apps, and for newly-launched processes that are sitting at the initial suspension point. The functionality in the previous versions of the API is still present (for example, desktop applications can still be launched).

.NET Framework Security

See Also

Reference

IVsDebugger4 Interface

Microsoft.VisualStudio.Shell.Interop Namespace