Home/ Questions/Q 519527
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T08:03:01+00:00

Running a c# console app I wrote on 64 bit Vista. Here’s the code:

  • 0

Running a c# console app I wrote on 64 bit Vista. Here’s the code:

class Class1
{
    static void Main(string[] args)
    {
        Debug.Assert(File.Exists(@"c:\test.ini"));
        StringBuilder sb = new StringBuilder(500);
        uint res = GetPrivateProfileString("AppName", "KeyName", "", sb, sb.Capacity, @"c:\test.ini");
        Console.WriteLine(sb.ToString());
    }
    [DllImport("kernel32.dll")]
    static extern uint GetPrivateProfileString(string lpAppName, string lpKeyName, string lpDefault, StringBuilder lpReturnedString, int nSize, string lpFileName);
}

I’m sure I’ll get a big “DUH!” for an answer, but I’m not seeing why this fails to work. Other than the Debug.Assert, this code was cut from the c# sample at this page

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This one has been busting my chops all day, too. I think I found a work-around, which I really don’t want to have to deal with: insert a blank line before the first section header in your .ini file. Now run your app and see if you don’t start seeing the values you were expecting.

    Considering this bug has apparently been around for years, I’m surprised MS hasn’t fixed it by now. But then, .ini files were supposed to have gone away years ago. Which of course is funny, because there are a lot of places MS uses .ini file (e.g, desktop.ini). But I think MS is aware of the bug, because I notice my desktop.ini files include a leading blank line. Hmmm…

    • 0