den4b Forum

therube

Member

Registered: 2010-05-24

Posts: 31

Ini Filename Should Be Named As .EXE Filename

Ini Filename Should Be Named As .EXE Filename

In 3a, that was the case, was convenient & identified the ini as belonging to a specific application (& version/naming convention as it was).

Currently, settings are named using the "generic" filename "Settings.ini".

In some cases, I'll throw a bunch of smaller, generally stand-alone utilities into a single directory.
Keeping the ini file named the same as the .exe differentiates it from others & identifies it to a particular program.
"Settings.ini" does not.

Doing this would be a benefit, IMO.

beyondo.ini
ELVIS.INI
Hasher_3a.ini
hwmonitorw.ini
i_view32.ini
HxD.ini
Lupas.ini
regshot.ini
Settings.ini
win32pad.ini
WizTree.ini

den4b

Administrator

From: den4b.com

Registered: 2006-04-06

Posts: 3,440

Re: Ini Filename Should Be Named As .EXE Filename

Generalizing file names (among other things) helps with development, maintenance and deployment processes. I expect all of the products soon to move to the generic "Settings.ini" naming convention.

In your case I would suggest placing Hasher in a separate folder to keep it self-contained.

---

A story of software development, and how it all evolves into Live vs Pro
Request a Wiki account | Reporting spam and abuse | Why did I get banned?