DebugPrefix
[This property is no longer available for use as of Windows Server 2012.]
This property is not supported.
**Windows Server 2008 R2, Windows Server 2008 and Windows Server 2003: **
Specifies the path to the debugger used to debug the resource. The following table summarizes the attributes of the DebugPrefix property.
Attribute | Value |
---|---|
Data type | Null-terminated Unicode string |
Access | Read/write |
Structure | CLUSPROP_SZ |
Maximum | None (but see Maximum Property Size.) |
Default | NULL |
Remarks
To use the DebugPrefix property, a resource must run in a separate Resource Monitor. The debugger specified by the DebugPrefix property is attached to the Resource Monitor. If the debugger is in a directory that is included in the path, DebugPrefix can be set to a relative path. Otherwise, a full path must be specified.
Setting the DebugPrefix property causes "-p <process id>" to be appended to the end of the debug command, where <process id> represents the process identifier for the Resource Monitor handling the resource.
For more information about debugging a resource, see Debugging a Resource DLL.
The CLUSPROP_SZ_DECLARE macro creates a CLUSPROP_SZ structure with an array of the correct size.
Examples
The property value portion of a property list entry for DebugPrefix can be set with the following example code:
WCHAR szDebugPrefixData[] = L"C:\\Bin\\Debug.exe";
CLUSPROP_SZ_DECLARE( DebugPrefixValue,
sizeof( szDebugPrefixData ) / sizeof( WCHAR ) );
DebugPrefixValue.Syntax.dw = CLUSPROP_SYNTAX_LIST_VALUE_SZ;
DebugPrefixValue.cbLength = sizeof( szDebugPrefixData );
StringCbCopy( DebugPrefixValue.sz,
DebugPrefixValue.cbLength,
szDebugPrefixData );
Requirements
Minimum supported client |
None supported |
Minimum supported server |
Windows Server 2003 Enterprise, Windows Server 2003 Datacenter |
End of client support |
None supported |
End of server support |
Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter |