PERSIST_FOLDER_TARGET_INFO structure (shobjidl_core.h)
Specifies a folder shortcut's target folder and its attributes. This structure is used by IPersistFolder3::GetFolderTargetInfo and IPersistFolder3::InitializeEx.
Syntax
typedef struct _PERSIST_FOLDER_TARGET_INFO {
PIDLIST_ABSOLUTE pidlTargetFolder;
WCHAR szTargetParsingName[260];
WCHAR szNetworkProvider[260];
DWORD dwAttributes;
int csidl;
} PERSIST_FOLDER_TARGET_INFO;
Members
pidlTargetFolder
Type: PIDLIST_ABSOLUTE
A fully qualified PIDL of the target folder. Set pidlTargetFolder to NULL if not specified.
szTargetParsingName[260]
Type: WCHAR[MAX_PATH]
A null-terminated Unicode string with the target folder's parsing name. Set szTargetParsingName to an empty string if not specified.
szNetworkProvider[260]
Type: WCHAR[MAX_PATH]
A null-terminated Unicode string that specifies the type of network provider that will be used when binding to the target folder. The format is the same as that used by the WNet API. Set szNetworkProvider to an empty string if not specified.
dwAttributes
Type: DWORD
A DWORD value that contains FILE_ATTRIBUTE_* flags as defined in Winnt.h. Set dwAttributes to -1 if not specified.
csidl
Type: int
The target folder's CSIDL value, if it has one. Set csidl to -1 if the target folder does not have a CSIDL. In addition to the CSIDL value, you can also set the following two flags.
CSIDL_FLAG_PFTI_TRACKTARGET
Indicates that the target folder should change if the user changes the target folder's underlying CSIDL value.
CSIDL_FLAG_CREATE
Indicates that the target folder should be created if it does not already exist.
Remarks
Any or all of the pidlTargetFolder, szTargetParsingName, and csidl members can be used to specify the target folder's location.
Requirements
Requirement | Value |
---|---|
Minimum supported client | Windows 2000 Professional, Windows XP [desktop apps only] |
Minimum supported server | Windows Server 2003 [desktop apps only] |
Header | shobjidl_core.h (include Shobjidl.h) |
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for