WritePrivateProfileString info  Overview  Group

The WritePrivateProfileString function copies a string into the specified section of the specified initialization file.

This function is provided for compatibility with 16-bit Windows-based applications. WIn32-based applications should store initialization information in the registry.

BOOL WritePrivateProfileString(

Parameters

lpAppName

Points to a null-terminated string containing the name of the section to which the string will be copied. If the section does not exist, it is created. The name of the section is case-independent; the string can be any combination of uppercase and lowercase letters.

lpKeyName

Points to the null-terminated string containing the name of the key to be associated with a string. If the key does not exist in the specified section, it is created. If this parameter is NULL, the entire section, including all entries within the section, is deleted.

lpString

Points to a null-terminated string to be written to the file. If this parameter is NULL, the key pointed to by the lpKeyName parameter is deleted.

Windows 95: This platform does not support the use of the TAB (\t) character as part of this parameter.

lpFileName

Points to a null-terminated string that names the initialization file.

Return Values

If the function successfully copies the string to the initialization file, the return value is nonzero.

If the function fails, or if it flushes the cached version of the most recently accessed initialization file, the return value is zero. To get extended error information, call GetLastError.

Remarks

Windows 95:

Windows 95 keeps a cached version of WIN.INI to improve performance. If all three parameters are NULL, the function flushes the cache. The function always returns FALSE after flushing the cache, regardless of whether the flush succeeds or fails.

A section in the initialization file must have the following form:

[section]
key=string
      .
      .
      . 

 

If the lpFileName parameter does not contain a full path and filename for the file, WritePrivateProfileString searches the Windows directory for the file. If the file does not exist, this function creates the file in the Windows directory.

If lpFileName contains a full path and filename and the file does not exist, WriteProfileString creates the file. The specified directory must already exist.

Windows NT:

Windows NT maps most .INI file references to the registry, using the mapping defined under the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\
        Windows NT\CurrentVersion\IniFileMapping

Windows NT keeps a cache for the IniFileMapping registry key. Calling WritePrivateProfileStringW with the value of all arguments set to NULL will cause Windows NT to refresh its cache of the IniFileMappingKey for the specified .INI file.

The Win32 Profile functions (Get/WriteProfile*, Get/WritePrivateProfile*) use the following steps to locate initialization information:

1. 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

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

An application using the WritePrivateProfileStringW function to enter .INI file information into the registry should follow these guidelines:

• Ensure that no .INI file of the specified name exists on the system.

• Ensure that there is a key entry in the registry that specifies the .INI file. This entry should be under the path HKEY_LOCAL_MACHINE\SOFTWARE \Microsoft\Windows NT\CurrentVersion\IniFileMapping.

• Specify a value for that .INI file key entry that specifies a section. That is to say, an application must specify a section name, as it would appear within an .INI file or registry entry. Here is an example: [My Section].

• For system files, specify SYS for an added value.

• For application files, specify USR within the added value. Here is an example: “My Section: USR: App Name\Section”. And, since USR indicates a mapping under HKEY_CURRENT_USER, the application should also create a key under HKEY_CURRENT_USER that specifies the application name listed in the added value. For the example just given, that would be “App Name”.

• After following the preceding steps, an application setup program should call WritePrivateProfileStringW with the first three parameters set to NULL, and the fourth parameter set to the INI filename. For example:

  WritePrivateProfileStringW( NULL, NULL, NULL, L"appname.ini" ); 
  
   

• Such a call causes the mapping of an .INI file to the registry to take effect before the next system reboot. The operating system re-reads the mapping information into shared memory. A user will not have to reboot their computer after installing an application in order to have future invocations of the application see the mapping of the .INI file to the registry.

The following sample code illustrates the preceding guidelines and is based on several assumptions:

• There is an application named “App Name.”

• That application uses an .INI file named “appname.ini.”

• There is a section in the .INI file that we want to look like this:

  [Section1] 
  
    FirstKey = It all worked out okay. 
  
    SecondKey = By golly, it works. 
  
    ThirdKey = Another test. 
  
   

• The user will not have to reboot the system in order to have future invocations of the application see the mapping of the .INI file to the registry.

Here is the sample code :

 

// include files 

#include <stdio.h> 

#include <windows.h> 

 

// a main function 

main() 

 

{ 

  // local variables 

  CHAR inBuf[80]; 

  HKEY  hKey1, hKey2; 

  DWORD  dwDisposition; 

  LONG   lRetCode; 

 

  // try to create the .INI file key 

  lRetCode = RegCreateKeyEx ( HKEY_LOCAL_MACHINE, 

                              "SOFTWARE\\Microsoft\\Windows NT 

                               \\CurrentVersion\\IniFileMapping\\appname.ini", 

                              0, NULL, REG_OPTION_NON_VOLATILE, KEY_WRITE, 

                              NULL, &hKey1, 

                              &dwDisposition); 

 

  // if we failed, note it, and leave 

  if (lRetCode != ERROR_SUCCESS){ 

    printf ("Error in creating appname.ini key\n"); 

    return (0) ; 

    } 

 

  // try to set a section value 

  lRetCode = RegSetValueEx ( hKey1, 

                             "Section1", 

                             0, 

                             REG_SZ, 

                             "USR:App Name\\Section1", 

                             20); 

 

  // if we failed, note it, and leave 

  if (lRetCode != ERROR_SUCCESS) { 

    printf ( "Error in setting Section1 value\n"); 

    return (0) ; 

    } 

 

  // try to create an App Name key 

  lRetCode = RegCreateKeyEx ( HKEY_CURRENT_USER, 

                              "App Name", 

                              0, NULL, REG_OPTION_NON_VOLATILE, KEY_WRITE, 

                              NULL, &hKey2, 

                              &dwDisposition); 

 

  // if we failed, note it, and leave 

  if (lRetCode != ERROR_SUCCESS) { 

    printf ("Error in creating App Name key\n"); 

    return (0) ; 

    } 

 

  // force the operating system to re-read the mapping into shared memory 

  //    so that future invocations of the application will see it 

  //    without the user having to reboot the system 

  WritePrivateProfileStringW( NULL, NULL, NULL, L"appname.ini" ); 

 

  // if we get this far, all has gone well 

  // let's write some added values 

  WritePrivateProfileString ("Section1", "FirstKey", 

                             "It all worked out okay.", "appname.ini"); 

  WritePrivateProfileString ("Section1", "SecondKey", 

                             "By golly, it works.", "appname.ini"); 

  WritePrivateProfileSection ("Section1", "ThirdKey = Another Test.", 

                              "appname.ini"); 

 

  // let's test our work 

  GetPrivateProfileString ("Section1", "FirstKey", 

                           "Bogus Value: Get didn't work", inBuf, 80, 

                           "appname.ini"); 

  printf ("%s", inBuf); 

 

  // okay, we are outta here 

  return(0); 

 

} 

 

See Also

GetPrivateProfileString, WriteProfileString

  .