I don't think it's all that bad... The use of .ini files is deprecated in .NET because we have much more structured and implicit ways of reading startup configuration.
On Sep 16, 5:14 pm, "Pankaj Kapoor" <[EMAIL PROTECTED]> wrote: > shit, i have to deal with a number of ini files in my app.. I wrote a C++ > app before that read from some existing ini files, and it did it well, but > now i have to make same app in C#.. Im gonna be fried :-( > > > > > > On Thu, Sep 11, 2008 at 9:50 PM, Glenn <[EMAIL PROTECTED]> wrote: > > Avoid .ini files if at all possible. The same task can be done easier and > > better through the use of an XML file. > > > If you absolutely must use an ini file, you have two choices: > > > 1. Write your own ini file processing class. The structure of the file is > > basic. > > 2. Use P/Invoke to interface to the old Windows API ini file routines. > > > Believe it or not, #1 is easier than #2. But, not using ini files is even > > easier. In fact, you can simply use the Properties class that is created by > > default in most .NET projects. > > > ...Glenn > > > On Wed, Sep 10, 2008 at 5:10 AM, uma <[EMAIL PROTECTED]> wrote: > > >> how can i read and write ini files using c# > > > -- > > ------------------------------------------------------ > >http://onefryshort.org/ > >http://blog.onefryshort.org/ > > ------------------------------------------------------ > > -- > Pankaj Kapoor > "Bigamy is having one wife too many. Monogamy is the same." Oscar Wilde- Hide > quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
