|
|
|
|
|
|
|
|
|
Quick Info
Windows NT
| Yes
| Win95
| Yes
| Win32s
| No
| Import Library
| kernel32.lib
| Header File
| winbase.h
| Unicode
| WinNT
| Platform Notes
| None
|
|
|
GetPrivateProfileSectionNames
The
GetPrivateProfileSectionNames function retrieves the names of all sections in an initialization file. This
function is provided for compatibility with 16-bit Windows-based applications.
Win32-based applications should store initialization information in the
registry.
DWORD GetPrivateProfileSectionNames(
LPTSTR lpszReturnBuffer,
| // address of return buffer
|
DWORD nSize,
| // size of return buffer
|
LPCTSTR lpFileName
| // address of initialization filename
|
);
|
|
Parameters
lpszReturnBuffer
Points to a buffer that receives the section names associated with the named
file. The buffer is filled with one or more null-terminated strings; the last
string is followed by a second null character.
nSize
Specifies the size, in characters, of the buffer pointed to by the
lpszReturnBuffer parameter.
lpFileName
Points to a null-terminated string that names the initialization file. If this
parameter is NULL, the function searches the WIN.INI file. If this parameter
does not contain a full path to the file, Windows searches for the file in the
Windows directory.
Return Values
The return value specifies the number of characters copied to the specified
buffer, not including the terminating null character. If the buffer is not large
enough to contain all the section names associated with the specified
initialization file, the return value is equal to the length specified by
nSize minus two.
Remarks
This operation is atomic; no updates to the initialization file are allowed
while the section names are being copied to the buffer.
Calls to profile functions might be mapped to the registry instead of to the
initialization files. When the operation has been mapped, the
GetPrivateProfileSectionNames function retrieves information from the registry, not from the initialization
file; the change in the storage location has no effect on the function's
behavior.
The Win32 Profile functions (
Get/WriteProfile*,
Get/WritePrivateProfile*) use the following steps to locate initialization information:
- Look in the registry for the name of the initialization file, say myfile.ini,
under IniFileMapping:
HKEY_LOCAL_MACHINE\
Software\
Microsoft\
Windows NT\
CurrentVersion\
IniFileMapping\myfile.ini
- Look for the section name specified by lpAppName. This will be a named value under myfile.ini, or a subkey of myfile.ini, or
will not exist.
- If the section name specified by lpAppName is a named value under myfile.ini, then that value specifies where in the
registry you will find the keys for the section.
- If the section name specified by lpAppName is a subkey of myfile.ini, then named values under that subkey specify where
in the registry you will find the keys for the section. If the key you are
looking for does not exist as a named value, then there will be an unnamed value
(shown as "<No Name>") that specifies the default location in the registry where
you will find the key.
- If the section name specified by lpAppName does not exist as a named value or as a subkey under myfile.ini, then there
will be an unnamed value (shown as "<No Name>") under myfile.ini that specifies
the default location in the registry where you will find the keys for the
section.
- If there is no subkey for myfile.ini, or if there is no entry for the section
name, then look for the actual myfile.ini on the disk and read its contents.
When looking at values in the registry that specify other registry locations,
there are several prefixes that change the behavior of the ini file mapping:
! - this character forces all writes to go both to the registry and to the
.INI file on disk.
# - this character causes the registry value to be set to the value in the
Windows 3.1 .INI file when a new user logs in for the first time after setup.
@ - this character prevents any reads from going to the .INI file on disk if
the requested data is not found in the registry.
USR: - this prefix stands for HKEY_CURRENT_USER, and the text after the prefix
is relative to that key.
SYS: - this prefix stands for HKEY_LOCAL_MACHINE\SOFTWARE, and the text after
the prefix is relative to that key.
See Also
GetPrivateProfileSection,
WritePrivateProfileSection
- Software for developers
-
Delphi Components
.Net Components
Software for Android Developers
- More information resources
-
MegaDetailed.Net
Unix Manual Pages
Delphi Examples
- Databases for Amazon shops developers
-
Amazon Categories Database
Browse Nodes Database