[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 135
  • Last Modified:

When did INI files in the C:\Windows folder become bad practice?

Back in the Windows 3.1 days, programs would store configuration data in .INI files stored in the C:\Windows folder.

Nowadays, of course, this isn't a good idea anymore and it is surpassed by newer technologies like the Registry, and saving data in the user's AppData folder. For lots and lots of good reasons.

Is there a SPECIFIC Microsoft reference article or KB article that discusses this change in best practices, or some other kind of documentation I can point at to say when this shift in thinking occured on Microsoft's part? Maybe some kind of "introduction to the Registry" document from '95?

I'm trying to convince a stubborn vendor to update their software.
0
Frosty555
Asked:
Frosty555
2 Solutions
 
andreasSystem AdminCommented:
0
 
goldiedCommented:
Hey, just Google for user account control. I've worked for a software vendor and anything that has to write to the c: drive in system folders or even in its own root folder will fail.

This is the reason for what was originally dubbed windows logo certification. Your vendor needs to become Microsoft certified in order to be fully compliant.

http://msdn.microsoft.com/en-gb/library/windows/desktop/dd371701%28v=vs.85%29.aspx
0
 
dbruntonCommented:
Probably Windows NT introduced the idea of using the Registry rather than ini files.

See http://en.wikipedia.org/wiki/Windows_Registry#Virtualization

If you read the article it DOES NOT mean that Windows will take care of the ini problem.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
BillDLCommented:
An interesting question was posed here:
http://blogs.msdn.com/b/oldnewthing/archive/2006/02/22/536920.aspx#536935
and it led to the posting of a pros vs cons blog entry here:
http://blogs.msdn.com/b/oldnewthing/archive/2007/11/26/6523907.aspx

It all depends on the complexity of the "program".  It would be practically impossible to store all the configuration data for an application suite like Microsoft Office in INI or XML-based config files, but for programs like IrfanView image editor, CCleaner, and so on, I see no compelling reason why the program settings should not be stored in an INI file in the program's own folder.
0
 
andreasSystem AdminCommented:
under win vista and up the c:\program files cannot be writteen to without admin rights. files wirtten with user rights end up in the profile folder of the user in some shadow directories, so the settings apply only rto this user created the file. if a file already persistent in the folder from installation and needs to be modified im not sure if a copy will go to the shadow dir or if it only can be modified with admin access. Thus putting files to the programs folder is laso no good way.
0
 
Éric MoreauSenior .Net ConsultantCommented:
I wouldn't agree that the registry is a better option over config files. When programming in .Net, you are encouraged to use App.Config files (a kind of INI file XML formatted) as one is already created when creating a new project.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now