297

Is there any class in the .NET framework that can read/write standard .ini files:

[Section]
<keyname>=<value>
...

Delphi has the TIniFile component and I want to know if there is anything similar for C#?

JasonMArcher
  • 14,195
  • 22
  • 56
  • 52
zendar
  • 13,384
  • 14
  • 59
  • 75
  • RemObjects has a Delphi Prism library called ShineOn that ships a similar INI file class. But you need to have Delphi Prism to compile it for .NET from source as there is not yet a compiled assembly available. http://code.remobjects.com/p/shineon/ – Lex Li Sep 27 '09 at 01:13
  • 2
    Got the same problem and made my own library for parsing ini files: https://github.com/rickyah/ini-parser/ Hope it helps – Ricardo Amores Feb 12 '15 at 15:54
  • 5
    Just like Ricky I decided to make my own solution to this. Its available on: https://github.com/MarioZ/MadMilkman.Ini – Mario Z May 06 '15 at 12:11

17 Answers17

293

Preface

Firstly, read this MSDN blog post on the limitations of INI files. If it suits your needs, read on.

This is a concise implementation I wrote, utilising the original Windows P/Invoke, so it is supported by all versions of Windows with .NET installed, (i.e. Windows 98 - Windows 11). I hereby release it into the public domain - you're free to use it commercially without attribution.

The tiny class

Add a new class called IniFile.cs to your project:

using System.IO;
using System.Reflection;
using System.Runtime.InteropServices;
using System.Text;

// Change this to match your program's normal namespace
namespace MyProg
{
    class IniFile   // revision 11
    {
        string Path;
        string EXE = Assembly.GetExecutingAssembly().GetName().Name;

        [DllImport("kernel32", CharSet = CharSet.Unicode)]
        static extern long WritePrivateProfileString(string Section, string Key, string Value, string FilePath);

        [DllImport("kernel32", CharSet = CharSet.Unicode)]
        static extern int GetPrivateProfileString(string Section, string Key, string Default, StringBuilder RetVal, int Size, string FilePath);

        public IniFile(string IniPath = null)
        {
            Path = new FileInfo(IniPath ?? EXE + ".ini").FullName;
        }

        public string Read(string Key, string Section = null)
        {
            var RetVal = new StringBuilder(255);
            GetPrivateProfileString(Section ?? EXE, Key, "", RetVal, 255, Path);
            return RetVal.ToString();
        }

        public void Write(string Key, string Value, string Section = null)
        {
            WritePrivateProfileString(Section ?? EXE, Key, Value, Path);
        }

        public void DeleteKey(string Key, string Section = null)
        {
            Write(Key, null, Section ?? EXE);
        }

        public void DeleteSection(string Section = null)
        {
            Write(null, null, Section ?? EXE);
        }

        public bool KeyExists(string Key, string Section = null)
        {
            return Read(Key, Section).Length > 0;
        }
    }
}

How to use it

Open the INI file in one of the 3 following ways:

// Creates or loads an INI file in the same directory as your executable
// named EXE.ini (where EXE is the name of your executable)
var MyIni = new IniFile();

// Or specify a specific name in the current dir
var MyIni = new IniFile("Settings.ini");

// Or specify a specific name in a specific dir
var MyIni = new IniFile(@"C:\Settings.ini");

You can write some values like so:

MyIni.Write("DefaultVolume", "100");
MyIni.Write("HomePage", "http://www.google.com");

To create a file like this:

[MyProg]
DefaultVolume=100
HomePage=http://www.google.com

To read the values out of the INI file:

var DefaultVolume = MyIni.Read("DefaultVolume");
var HomePage = MyIni.Read("HomePage");

Optionally, you can set [Section]'s:

MyIni.Write("DefaultVolume", "100", "Audio");
MyIni.Write("HomePage", "http://www.google.com", "Web");

To create a file like this:

[Audio]
DefaultVolume=100

[Web]
HomePage=http://www.google.com

You can also check for the existence of a key like so:

if(!MyIni.KeyExists("DefaultVolume", "Audio"))
{
    MyIni.Write("DefaultVolume", "100", "Audio");
}

You can delete a key like so:

MyIni.DeleteKey("DefaultVolume", "Audio");

You can also delete a whole section (including all keys) like so:

MyIni.DeleteSection("Web");

Please feel free to comment with any improvements!

Leo
  • 5
  • 4
Danny Beckett
  • 20,529
  • 24
  • 107
  • 134
  • 11
    I'm little late, but it's missing `GetSections()` method. – stil Jan 19 '16 at 10:25
  • 3
    Maybe a more traditional default would be per-application (not per-assembly) .ini files like `Path.GetFullPath(IniPath ?? Path.ChangeExtension(Application.ExecutablePath, ".ini"))`. – Eugene Ryabtsev Apr 21 '16 at 10:44
  • 3
    Really great ! Put it on github ? – Emrys Myrooin Jul 06 '16 at 14:26
  • What's the advantage of using P/Invoke other than backwards compatability? – user3791372 Oct 16 '16 at 14:13
  • Due to the `Assembly.GetExecutingAssembly().GetName().Name` this doesn't play nicely when used in a `common` library as it'll expect the section header to be the name of the IniFile library rather than your application. – user3791372 Oct 16 '16 at 14:53
  • 2
    @danny Beckett, nicely done. This is nearly exactly like the same as what I've used for the past um-years of .Net. Upgraded from old code years ago. – Damian Jan 12 '17 at 15:03
  • 14
    Old now, and as much as I respect Raymond Chen, many of the limitations in that article were limitations of the specific INI library in Windows, and not the INI format itself. Others, like granular permissions, could be easily sidestepped via multiple files. An **official**, modernized INI library would be most-welcomed, even today. – Joel Coehoorn Jan 31 '17 at 01:44
  • 2
    Reading is not working, Can you give another easy example reading value by providing key only? – Touhid Sep 24 '18 at 08:47
  • @Touhid There must be some problem with your project or code. The function has worked for a long time, and the class code hasn't changed. – Danny Beckett Sep 26 '18 at 00:54
  • To work the solution, section is must to specify in INI file as well in read() method. – Sushil Jadhav Dec 14 '18 at 08:29
  • @JSushil Good spot! This only applies to .ini files where sections are used, however. I.e. you don't need to specify anything if you're using a flat-style without sections. – Danny Beckett Dec 16 '18 at 13:21
  • 1
    This code works well! However I have a problem with the encoding. My INI file contains Japanese characters. When I use the above code to read it, the result contains strange chars. Can you help on this one? – Leonard AB Mar 22 '19 at 05:32
  • How could i get the total keys of one section and foreach their keys to get the keys name and values? Thank you! – user3790692 Mar 22 '19 at 19:43
  • 1
    Why do you restrict the return buffer size of Read() to 255 characters, when the underlying API doesn't impose such limitation? – zett42 Mar 28 '19 at 14:57
  • 1
    @zett42 That's a great question! What value are you able to use? I'm going to do another revision of this code soon, taking into account some of the comments above, so thanks! – Danny Beckett Mar 31 '19 at 09:35
  • 1
    According to [this answer](https://stackoverflow.com/a/54506764/7571258), the maximum buffer size accepted by `GetPrivateProfileString()` appears to be 65536 (including null-terminator). – zett42 Mar 31 '19 at 10:33
  • 1
    This will only work on Windows, and so breaks the multi-platform compatibility of your software. A high cost for such a small functionality. – Nohus Apr 04 '19 at 10:10
  • 1
    it's a selfish plug, but the issues raised in commentary with this approach (cross-platform issues, limitations of the underlying win32 ini parser (of which I'm well aware)) are resolved with PeanutButter.INI (get it from nuget or find PeanutButter on github). I'm the author (hence the intro), but I'm responsive to issues. PB.INI also preserves commentary. Warning: the code is not super-pretty, but it works quite well and is actively maintained. – daf Dec 25 '19 at 17:29
  • 1
    There is no error management if section or key has not be found. It could use the GetLastError() function to retrieve if an error occured. See https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-getprivateprofilestring –  Apr 08 '20 at 12:10
  • You should add this in **github** its very easy to use thanks – Haseeb Mir Jul 26 '20 at 18:09
  • @DannyBeckett Thanks a lot for this, I also needed a quick way to store some simple settings for a small app, otherwise I agree on the scoping of using .ini files nowadays. One small note, the Read(...) method does not work out of "the box" because you expect a Section to not be null there, so it kind-of makes using sections mandatory. I can use it like this for my purpose, but maybe you want to change that a bit. I see that also some other people mentioned they cannot read keys. Cheers! – Florin Mircea Oct 02 '21 at 16:38
  • awesome , thank you for the class , one thing i'm curious about is : if the user use something like = or " , some sort of an injection would that break the ini file ? , its not that the user will do it intentionally , but it can happen by mistake from users that are not aware of this things – The Doctor Jul 20 '22 at 10:56
  • 1
    Reading not working. I need it for a ini file. Exist a solution? – AxelS Nov 08 '22 at 04:54
  • great! relevant question/answer to this day! 14 year old question, amazing – SammuelMiranda May 03 '23 at 14:49
213

The creators of the .NET framework want you to use XML-based config files, rather than INI files. So no, there is no built-in mechanism for reading them.

There are third party solutions available, though.

Palec
  • 12,743
  • 8
  • 69
  • 138
David Arno
  • 42,717
  • 16
  • 86
  • 131
  • 7
    @aloneguid I would argue that the large set of available features actually contributed to .NET config files ending up being strange behemoths with a lot of magic in them. They have become "code in the config file," and this leads to a lot of complexity, strange behaviors, and makes configuration management more difficult. (I'm looking at you, database "providers" and connection strings.) So INI files are also generally better for non-manual editing, as well. – jpmc26 Mar 16 '17 at 02:51
  • 1
    i like old method (P/Inovke) and you can use unicode with old method like this: File.WriteAllBytes(path, new byte[] { 0xFF, 0xFE }); – sailfish009 Jul 08 '18 at 01:22
  • 2
    Good package but it could be better. It can not parse a value that contains '=' Or '\n' completely – Ahmad Behjati Oct 13 '19 at 09:16
67

This article on CodeProject "An INI file handling class using C#" should help.

The author created a C# class "Ini" which exposes two functions from KERNEL32.dll. These functions are: WritePrivateProfileString and GetPrivateProfileString. You will need two namespaces: System.Runtime.InteropServices and System.Text.

Steps to use the Ini class

In your project namespace definition add

using INI;

Create a INIFile like this

INIFile ini = new INIFile("C:\\test.ini");

Use IniWriteValue to write a new value to a specific key in a section or use IniReadValue to read a value FROM a key in a specific Section.

Note: if you're beginning from scratch, you could read this MSDN article: How to: Add Application Configuration Files to C# Projects. It's a better way for configuring your application.

splattne
  • 102,760
  • 52
  • 202
  • 249
  • 1
    I want to read complete INI file. How to do the same instead of reading section,key – venkat Mar 11 '10 at 10:36
  • this worked for me, and then stopped working from another point. No idea still what went different under the hood – nawfal Jun 08 '12 at 08:55
  • 2
    Watch out using this deprecated Win32 API functions. More info: http://stackoverflow.com/questions/11451641/writeprivateprofilestring-is-not-adding-proprty-to-the-end – Pedro77 Jun 21 '14 at 22:28
  • 1
    I used this approach for awhile, but security enhancements starting in Win7 have pretty much killed this for me. You can still use this approach, but you will have store the .ini in ProgramData and have your app read / write there. – Jess Sep 04 '14 at 04:48
  • 1
    Do not save application configuration ini files in ProgramData. They do not belong in either the Registry or ProgramData. Config files are supposed to be in the LocalApplicationData folders. – deegee May 02 '15 at 01:02
  • Simple INI file reader/writer which served my purpose without bloated library code. :) – Naveen Kumar V Apr 07 '23 at 08:46
49

I found this simple implementation:

http://bytes.com/topic/net/insights/797169-reading-parsing-ini-file-c

Works well for what I need.

Here is how you use it:

public class TestParser
{
    public static void Main()
    {
        IniParser parser = new IniParser(@"C:\test.ini");

        String newMessage;

        newMessage = parser.GetSetting("appsettings", "msgpart1");
        newMessage += parser.GetSetting("appsettings", "msgpart2");
        newMessage += parser.GetSetting("punctuation", "ex");

        //Returns "Hello World!"
        Console.WriteLine(newMessage);
        Console.ReadLine();
    }
}

Here is the code:

using System;
using System.IO;
using System.Collections;

public class IniParser
{
    private Hashtable keyPairs = new Hashtable();
    private String iniFilePath;

    private struct SectionPair
    {
        public String Section;
        public String Key;
    }

    /// <summary>
    /// Opens the INI file at the given path and enumerates the values in the IniParser.
    /// </summary>
    /// <param name="iniPath">Full path to INI file.</param>
    public IniParser(String iniPath)
    {
        TextReader iniFile = null;
        String strLine = null;
        String currentRoot = null;
        String[] keyPair = null;

        iniFilePath = iniPath;

        if (File.Exists(iniPath))
        {
            try
            {
                iniFile = new StreamReader(iniPath);

                strLine = iniFile.ReadLine();

                while (strLine != null)
                {
                    strLine = strLine.Trim().ToUpper();

                    if (strLine != "")
                    {
                        if (strLine.StartsWith("[") && strLine.EndsWith("]"))
                        {
                            currentRoot = strLine.Substring(1, strLine.Length - 2);
                        }
                        else
                        {
                            keyPair = strLine.Split(new char[] { '=' }, 2);

                            SectionPair sectionPair;
                            String value = null;

                            if (currentRoot == null)
                                currentRoot = "ROOT";

                            sectionPair.Section = currentRoot;
                            sectionPair.Key = keyPair[0];

                            if (keyPair.Length > 1)
                                value = keyPair[1];

                            keyPairs.Add(sectionPair, value);
                        }
                    }

                    strLine = iniFile.ReadLine();
                }

            }
            catch (Exception ex)
            {
                throw ex;
            }
            finally
            {
                if (iniFile != null)
                    iniFile.Close();
            }
        }
        else
            throw new FileNotFoundException("Unable to locate " + iniPath);

    }

    /// <summary>
    /// Returns the value for the given section, key pair.
    /// </summary>
    /// <param name="sectionName">Section name.</param>
    /// <param name="settingName">Key name.</param>
    public String GetSetting(String sectionName, String settingName)
    {
        SectionPair sectionPair;
        sectionPair.Section = sectionName.ToUpper();
        sectionPair.Key = settingName.ToUpper();

        return (String)keyPairs[sectionPair];
    }

    /// <summary>
    /// Enumerates all lines for given section.
    /// </summary>
    /// <param name="sectionName">Section to enum.</param>
    public String[] EnumSection(String sectionName)
    {
        ArrayList tmpArray = new ArrayList();

        foreach (SectionPair pair in keyPairs.Keys)
        {
            if (pair.Section == sectionName.ToUpper())
                tmpArray.Add(pair.Key);
        }

        return (String[])tmpArray.ToArray(typeof(String));
    }

    /// <summary>
    /// Adds or replaces a setting to the table to be saved.
    /// </summary>
    /// <param name="sectionName">Section to add under.</param>
    /// <param name="settingName">Key name to add.</param>
    /// <param name="settingValue">Value of key.</param>
    public void AddSetting(String sectionName, String settingName, String settingValue)
    {
        SectionPair sectionPair;
        sectionPair.Section = sectionName.ToUpper();
        sectionPair.Key = settingName.ToUpper();

        if (keyPairs.ContainsKey(sectionPair))
            keyPairs.Remove(sectionPair);

        keyPairs.Add(sectionPair, settingValue);
    }

    /// <summary>
    /// Adds or replaces a setting to the table to be saved with a null value.
    /// </summary>
    /// <param name="sectionName">Section to add under.</param>
    /// <param name="settingName">Key name to add.</param>
    public void AddSetting(String sectionName, String settingName)
    {
        AddSetting(sectionName, settingName, null);
    }

    /// <summary>
    /// Remove a setting.
    /// </summary>
    /// <param name="sectionName">Section to add under.</param>
    /// <param name="settingName">Key name to add.</param>
    public void DeleteSetting(String sectionName, String settingName)
    {
        SectionPair sectionPair;
        sectionPair.Section = sectionName.ToUpper();
        sectionPair.Key = settingName.ToUpper();

        if (keyPairs.ContainsKey(sectionPair))
            keyPairs.Remove(sectionPair);
    }

    /// <summary>
    /// Save settings to new file.
    /// </summary>
    /// <param name="newFilePath">New file path.</param>
    public void SaveSettings(String newFilePath)
    {
        ArrayList sections = new ArrayList();
        String tmpValue = "";
        String strToSave = "";

        foreach (SectionPair sectionPair in keyPairs.Keys)
        {
            if (!sections.Contains(sectionPair.Section))
                sections.Add(sectionPair.Section);
        }

        foreach (String section in sections)
        {
            strToSave += ("[" + section + "]\r\n");

            foreach (SectionPair sectionPair in keyPairs.Keys)
            {
                if (sectionPair.Section == section)
                {
                    tmpValue = (String)keyPairs[sectionPair];

                    if (tmpValue != null)
                        tmpValue = "=" + tmpValue;

                    strToSave += (sectionPair.Key + tmpValue + "\r\n");
                }
            }

            strToSave += "\r\n";
        }

        try
        {
            TextWriter tw = new StreamWriter(newFilePath);
            tw.Write(strToSave);
            tw.Close();
        }
        catch (Exception ex)
        {
            throw ex;
        }
    }

    /// <summary>
    /// Save settings back to ini file.
    /// </summary>
    public void SaveSettings()
    {
        SaveSettings(iniFilePath);
    }
}
joerage
  • 4,863
  • 4
  • 38
  • 48
26

The code in joerage's answer is inspiring.

Unfortunately, it changes the character casing of the keys and does not handle comments. So I wrote something that should be robust enough to read (only) very dirty INI files and allows to retrieve keys as they are.

It uses some LINQ, a nested case insensitive string dictionary to store sections, keys and values, and read the file in one go.

using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;

class IniReader
{
    Dictionary<string, Dictionary<string, string>> ini = new Dictionary<string, Dictionary<string, string>>(StringComparer.InvariantCultureIgnoreCase);

    public IniReader(string file)
    {
        var txt = File.ReadAllText(file);

        Dictionary<string, string> currentSection = new Dictionary<string, string>(StringComparer.InvariantCultureIgnoreCase);

        ini[""] = currentSection;

        foreach(var line in txt.Split(new[]{"\n"}, StringSplitOptions.RemoveEmptyEntries)
                               .Where(t => !string.IsNullOrWhiteSpace(t))
                               .Select(t => t.Trim()))
        {
            if (line.StartsWith(";"))
                continue;

            if (line.StartsWith("[") && line.EndsWith("]"))
            {
                currentSection = new Dictionary<string, string>(StringComparer.InvariantCultureIgnoreCase);
                ini[line.Substring(1, line.LastIndexOf("]") - 1)] = currentSection;
                continue;
            }

            var idx = line.IndexOf("=");
            if (idx == -1)
                currentSection[line] = "";
            else
                currentSection[line.Substring(0, idx)] = line.Substring(idx + 1);
        }
    }

    public string GetValue(string key)
    {
        return GetValue(key, "", "");
    }

    public string GetValue(string key, string section)
    {
        return GetValue(key, section, "");
    }

    public string GetValue(string key, string section, string @default)
    {
        if (!ini.ContainsKey(section))
            return @default;

        if (!ini[section].ContainsKey(key))
            return @default;

        return ini[section][key];
    }

    public string[] GetKeys(string section)
    {
        if (!ini.ContainsKey(section))
            return new string[0];

        return ini[section].Keys.ToArray();
    }

    public string[] GetSections()
    {
        return ini.Keys.Where(t => t != "").ToArray();
    }
}
Larry
  • 17,605
  • 9
  • 77
  • 106
  • 5
    and thank you for not putting that `catch (Exception ex) { throw ex; }` in there – Mark Schultheiss Dec 18 '15 at 20:03
  • 2
    Good! At least some changes are required to work better. Line 16: ini[""] = currentSection; To: //ini[""] = currentSection; This must be removed as every time the first element [0] will be an empty segment due to this initialization. Line 36: currentSection[line.Substring(0, idx)] = line.Substring(idx + 1); To: currentSection[line.Substring(0, idx).Trim()] = line.Substring(idx + 1).Trim(); Key and values should be independently trimmed, not only on the line Trim. In INI like configuration files usually who add K->V pairs tend to align these equals inside sections. Thank you! – LXSoft Jun 04 '18 at 15:47
  • Wew been à long time. Thanks a lot for your suggestions. They all make sense and deserves this code to have a good refresh. – Larry Jun 04 '18 at 16:30
16

I want to introduce an IniParser library I've created completely in c#, so it contains no dependencies in any OS, which makes it Mono compatible. Open Source with MIT license -so it can be used in any code.

You can check out the source in GitHub, and it is also available as a NuGet package

It's heavily configurable, and really simple to use.

Sorry for the shameless plug but I hope it can be of help of anyone revisiting this answer.

Ricardo Amores
  • 4,597
  • 1
  • 31
  • 45
12

If you only need read access and not write access and you are using the Microsoft.Extensions.Confiuration (comes bundled in by default with ASP.NET Core but works with regular programs too) you can use the NuGet package Microsoft.Extensions.Configuration.Ini to import ini files in to your configuration settings.

public Startup(IHostingEnvironment env)
{
    var builder = new ConfigurationBuilder()
        .SetBasePath(env.ContentRootPath)
        .AddIniFile("SomeConfig.ini", optional: false);
    Configuration = builder.Build();
}
Scott Chamberlain
  • 124,994
  • 33
  • 282
  • 431
  • 1
    Just to add that you then get keys with `Configuration["keyname"]` – kofifus Aug 27 '19 at 23:32
  • @scott the issue I'm having is for whatever reason IIS does not recognize it when the app is running. it is deployed, and there, but is not being consumed. HTTP 500.30 returned and the IIS App log says "the configuration file was not found and is not optional." – one.beat.consumer Feb 01 '20 at 00:21
5

PeanutButter.INI is a Nuget-packaged class for INI files manipulation. It supports read/write, including comments – your comments are preserved on write. It appears to be reasonably popular, is tested and easy to use. It's also totally free and open-source.

Disclaimer: I am the author of PeanutButter.INI.

Palec
  • 12,743
  • 8
  • 69
  • 138
daf
  • 1,289
  • 11
  • 16
4

If you want just a simple reader without sections and any other dlls here is simple solution:

using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace Tool
{
    public class Config
    {
        Dictionary <string, string> values;
        public Config (string path)
        {
            values = File.ReadLines(path)
            .Where(line => (!String.IsNullOrWhiteSpace(line) && !line.StartsWith("#")))
            .Select(line => line.Split(new char[] { '=' }, 2, 0))
            .ToDictionary(parts => parts[0].Trim(), parts => parts.Length>1?parts[1].Trim():null);
        }
        public string Value (string name, string value=null)
        {
            if (values!=null && values.ContainsKey(name))
            {
                return values[name];
            }
            return value;
        }
    }
}

Usage sample:

    file = new Tool.Config (Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location) + "\\config.ini");
    command = file.Value ("command");
    action = file.Value ("action");
    string value;
    //second parameter is default value if no key found with this name
    value = file.Value("debug","true");
    this.debug = (value.ToLower()=="true" || value== "1");
    value = file.Value("plain", "false");
    this.plain = (value.ToLower() == "true" || value == "1");

Config file content meanwhile (as you see supports # symbol for line comment):

#command to run
command = php

#default script
action = index.php

#debug mode
#debug = true

#plain text mode
#plain = false

#icon = favico.ico
BIOHAZARD
  • 1,937
  • 20
  • 23
4

Usually, when you create applications using C# and the .NET framework, you will not use INI files. It is more common to store settings in an XML-based configuration file or in the registry. However, if your software shares settings with a legacy application it may be easier to use its configuration file, rather than duplicating the information elsewhere.

The .NET framework does not support the use of INI files directly. However, you can use Windows API functions with Platform Invocation Services (P/Invoke) to write to and read from the files. In this link we create a class that represents INI files and uses Windows API functions to manipulate them. Please go through the following link.

Reading and Writing INI Files

Unknown
  • 721
  • 1
  • 8
  • 12
  • 4
    Stay out of the Registry! Application configuration data should not be saved in the Registry. – deegee May 02 '15 at 01:00
  • @deegee: Funny, since Microsoft says [INI file are deprecated in favor of the registry](https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-getprivateprofilestring). – Thomas Weller Dec 20 '21 at 10:00
  • 1
    @ThomasWeller - I'm not here to argue with people. The Registry should never be used unless it is absolutely necessary. And even then it should be reserved for Microsoft Windows use only. Virtually no third-party software cleans up their Registry keys when you uninstall their software, leaving the Registry in a state of mess, which they should have stayed out of to begin with. INI files, XML files, JSON files, and other configuration file formats designed specifically for this function should be placed into the AppData folder where they are SUPPOSED to go. – deegee Dec 22 '21 at 09:36
3

Try this method:

public static Dictionary<string, string> ParseIniDataWithSections(string[] iniData)
{
    var dict = new Dictionary<string, string>();
    var rows = iniData.Where(t => 
        !String.IsNullOrEmpty(t.Trim()) && !t.StartsWith(";") && (t.Contains('[') || t.Contains('=')));
    if (rows == null || rows.Count() == 0) return dict;
    string section = "";
    foreach (string row in rows)
    {
        string rw = row.TrimStart();
        if (rw.StartsWith("["))
            section = rw.TrimStart('[').TrimEnd(']');
        else
        {
            int index = rw.IndexOf('=');
            dict[section + "-" + rw.Substring(0, index).Trim()] = rw.Substring(index+1).Trim().Trim('"');
        }
    }
    return dict;
}

It creates the dictionary where the key is "-". You can load it like this:

var dict = ParseIniDataWithSections(File.ReadAllLines(fileName));
Petr Voborník
  • 1,249
  • 1
  • 14
  • 11
3

I'm late to join the party, but I had the same issue today and I've written the following implementation:

using System.Text.RegularExpressions;

static bool match(this string str, string pat, out Match m) =>
    (m = Regex.Match(str, pat, RegexOptions.IgnoreCase)).Success;

static void Main()
{
    Dictionary<string, Dictionary<string, string>> ini = new Dictionary<string, Dictionary<string, string>>();
    string section = "";

    foreach (string line in File.ReadAllLines(.........)) // read from file
    {
        string ln = (line.Contains('#') ? line.Remove(line.IndexOf('#')) : line).Trim();

        if (ln.match(@"^[ \t]*\[(?<sec>[\w\-]+)\]", out Match m))
            section = m.Groups["sec"].ToString();
        else if (ln.match(@"^[ \t]*(?<prop>[\w\-]+)\=(?<val>.*)", out m))
        {
            if (!ini.ContainsKey(section))
                ini[section] = new Dictionary<string, string>();

            ini[section][m.Groups["prop"].ToString()] = m.Groups["val"].ToString();
        }
    }


    // access the ini file as follows:
    string content = ini["section"]["property"];
}

It must be noted, that this implementation does not handle sections or properties which are not found. To achieve this, you should extend the Dictionary<,>-class to handle unfound keys.


To serialize an instance of Dictionary<string, Dictionary<string, string>> to an .ini-file, I use the following code:

string targetpath = .........;
Dictionary<string, Dictionary<string, string>> ini = ........;
StringBuilder sb = new StringBuilder();

foreach (string section in ini.Keys)
{
    sb.AppendLine($"[{section}]");

    foreach (string property in ini[section].Keys)
        sb.AppendLine($"{property}={ini[section][property]");
}

File.WriteAllText(targetpath, sb.ToString());
unknown6656
  • 2,765
  • 2
  • 36
  • 52
2

There is an Ini Parser available in CommonLibrary.NET

This has various very convenient overloads for getting sections/values and is very light weight.

james
  • 236
  • 3
  • 3
  • 1
    In case it's not obvious from looking at the top level of the library (it wasn't obvious to me!), the IniDcoument class et al are in ComLib.IO. – Tim Keating Apr 21 '10 at 15:50
  • 2
    For anyone looking at this route, CommonLibrary.NET does not seem to follow .INI conventions. It uses a colon ":" as the delimiter instead of equals sign, and it does not handle comments (beginning a line with a semi-colon or pound sign will cause parsing to fail). – jmmr Dec 02 '13 at 22:26
2

Here is my own version, using regular expressions. This code assumes that each section name is unique - if however this is not true - it makes sense to replace Dictionary with List. This function supports .ini file commenting, starting from ';' character. Section starts normally [section], and key value pairs also comes normally "key = value". Same assumption as for sections - key name is unique.

/// <summary>
/// Loads .ini file into dictionary.
/// </summary>
public static Dictionary<String, Dictionary<String, String>> loadIni(String file)
{
    Dictionary<String, Dictionary<String, String>> d = new Dictionary<string, Dictionary<string, string>>();

    String ini = File.ReadAllText(file);

    // Remove comments, preserve linefeeds, if end-user needs to count line number.
    ini = Regex.Replace(ini, @"^\s*;.*$", "", RegexOptions.Multiline);

    // Pick up all lines from first section to another section
    foreach (Match m in Regex.Matches(ini, "(^|[\r\n])\\[([^\r\n]*)\\][\r\n]+(.*?)(\\[([^\r\n]*)\\][\r\n]+|$)", RegexOptions.Singleline))
    {
        String sectionName = m.Groups[2].Value;
        Dictionary<String, String> lines = new Dictionary<String, String>();

        // Pick up "key = value" kind of syntax.
        foreach (Match l in Regex.Matches(ini, @"^\s*(.*?)\s*=\s*(.*?)\s*$", RegexOptions.Multiline))
        {
            String key = l.Groups[1].Value;
            String value = l.Groups[2].Value;

            // Open up quotation if any.
            value = Regex.Replace(value, "^\"(.*)\"$", "$1");

            if (!lines.ContainsKey(key))
                lines[key] = value;
        }

        if (!d.ContainsKey(sectionName))
            d[sectionName] = lines;
    }

    return d;
}
TarmoPikaro
  • 4,723
  • 2
  • 50
  • 62
0

If you don't need bells and whistles (ie sections) here's a one liner:

List<(string, string)> ini = File.ReadLines(filename)
  .Select(s => {
     var spl = s.Split('=', 2);
     return spl.Length == 2 ? (spl[0], spl[1]) : (s, "");
   })
   .Select(vt => (vt.Item1.Trim(), vt.Item2.Trim()))
   .Where(vt => vt.Item1 != "")
   .ToList();

To write:

File.WriteAllLines(filename, ini.Select(vt => $"{vt.Item1}={vt.Item2}"));

(if you don't care about duplicates use .ToDictionary() instead of .ToList() for easier access)

kofifus
  • 17,260
  • 17
  • 99
  • 173
-4

Here is my class, works like a charm :

public static class IniFileManager
{


    [DllImport("kernel32")]
    private static extern long WritePrivateProfileString(string section,
        string key, string val, string filePath);
    [DllImport("kernel32")]
    private static extern int GetPrivateProfileString(string section,
             string key, string def, StringBuilder retVal,
        int size, string filePath);
    [DllImport("kernel32.dll")]
    private static extern int GetPrivateProfileSection(string lpAppName,
             byte[] lpszReturnBuffer, int nSize, string lpFileName);


    /// <summary>
    /// Write Data to the INI File
    /// </summary>
    /// <PARAM name="Section"></PARAM>
    /// Section name
    /// <PARAM name="Key"></PARAM>
    /// Key Name
    /// <PARAM name="Value"></PARAM>
    /// Value Name
    public static void IniWriteValue(string sPath,string Section, string Key, string Value)
    {
        WritePrivateProfileString(Section, Key, Value, sPath);
    }

    /// <summary>
    /// Read Data Value From the Ini File
    /// </summary>
    /// <PARAM name="Section"></PARAM>
    /// <PARAM name="Key"></PARAM>
    /// <PARAM name="Path"></PARAM>
    /// <returns></returns>
    public static string IniReadValue(string sPath,string Section, string Key)
    {
        StringBuilder temp = new StringBuilder(255);
        int i = GetPrivateProfileString(Section, Key, "", temp,
                                        255, sPath);
        return temp.ToString();

    }

}

The use is obviouse since its a static class, just call IniFileManager.IniWriteValue for readsing a section or IniFileManager.IniReadValue for reading a section.

Erwin Draconis
  • 764
  • 8
  • 20
  • This approach has already been shown and explained in [another answer](https://stackoverflow.com/a/14906422/2157640). What does your answer add that's not covered by that one? – Palec Oct 02 '18 at 07:53
  • Beware that it works only if .ini file is saved in UNICODE (16bit LE). Use Notepad++ to convert the text to unicode, because if you save it in UTF-8 wont work. Also ANSI is acceptable, but you cannot read accented letters – user2991288 Jan 17 '20 at 17:54
-8

You should read and write data from xml files since you can save a whole object to xml and also you can populate a object from a saved xml. It is better an easy to manipulate objects.

Here is how to do it: Write Object Data to an XML File: https://msdn.microsoft.com/en-us/library/ms172873.aspx Read Object Data from an XML File: https://msdn.microsoft.com/en-us/library/ms172872.aspx

Daniel
  • 273
  • 4
  • 18
  • 1
    Links to external resources are encouraged, but please add context around the link so your fellow users will have some idea what it is and why it’s there. Always quote the most relevant part of an important link, in case the target site is unreachable or goes permanently offline. – davejal Jan 13 '16 at 02:04
  • I believe that the links titles are very clear about its references/context. If you think that´s not enough feel free to edit it. – Daniel Jan 13 '16 at 14:55
  • 3
    Does not address the actual question. – Erik Knowles May 05 '16 at 21:29