This class can store information from an ini into memory rather than the API calls where you constantly open and close the same file over and over. It also does not require to load from a file, eg. if you have the ini code in a database then you can simply retreive the data and process it with the InputINI function rather than having to save it into to process it. Since it uses a Dictionary object you can process every key and/or section if you need to. This is very useful for loading massive amounts, saving a lot of processing time. (eg. if you wanted to load 600 different keys in a file, the IniClass only needs to open it once)
It requires Microsoft Scripting Runtime in your application
Last edited by Doomguy0505; Oct 3rd, 2006 at 11:55 PM.
There is a good reason why the API calls Lock/Read/Write/Unlock on every access: concurrency.
But when your application isn't worried about the INI file being accessed by multiple processes (or threads for that matter) this is a decent way to go.