Nature, and this one should be no different.Īside from getting and setting key values, I want to able to add, remove andĮdit sections. Ultimately text files, and there is no reason they can't be handled as such.įurthermore, I don't want to be limited by the Get/Set nature of the I suppose people think that this would make things faster, I'm not sure whyĮvery reference to *.ini files begins and ends with accessing the I decided to write my own class to handle this function. Native support for this storage solution in. Would have you store this information in an XML file, but the fact is that manyĮnd users (and even many programmers) still prefer the simple to open/editįormat of the venerable old *.ini file. Should be able to copy settings along with the executable and go. Registry, but this defeats the XCopy deployment paradigm of. Many programmers choose to store their custom program settings in the I searched on Google for a better solution, but found nothing. ( WritePrivateProfileString, GetPrivateProfileString). Its reliance on the Kernel32.dll *.ini file functions Offered some Getval/ Setval functions and a customįunction to Get/Set your form settings quickly. This wasĪ great idea, but the code presented was extremely limited, and basically only To build a custom class to save your winform settings to an *.ini file. The February 2004 edition of MSDN magazine included some example code on how
0 Comments
Leave a Reply. |