Sujet : Re: Does Dimdows Know What Time It Is?
De : bowman (at) *nospam* montana.com (rbowman)
Groupes : comp.os.linux.advocacyDate : 04. Oct 2024, 22:20:33
Autres entêtes
Message-ID : <lmb4h1F4ppiU13@mid.individual.net>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
User-Agent : Pan/0.149 (Bellevue; 4c157ba)
On Fri, 4 Oct 2024 07:54:39 -0400, Chris Ahlstrom wrote:
Actually that is preferable to an ever expanding database with legacy
32-bit stuff plus 64-bit duplicate stuff (and don't get me started on
the system32 directory).
Yeah, SysWOW64 was one of MS's weirder moves. Odbcad32.exe was the real
pisser. Both the 32 and 64 bit versions are called Odbcad32.exe. Our
legacy programs are 32 bit so inadvertently using the 64bit one to create
a DSN loads a 64bit driver which doesn't fly.
To me, it's nice to have one small config file for each "application".
Most of the later native Windows work I've done uses C# with a JSON
configuration file. I create an installer that drops the exe, required
dlls, and the configuration file in the specified directory.
IConfiguration config = new ConfigurationBuilder()
.AddJsonFile("rangechecker.json")
.AddEnvironmentVariables()
.Build();
string database = config["Database"];
string dataType = config["DataType"];
.....
makes it easy to pick up the specific configuration plus any global
environment variables you need. I've gotten fond of C# and DotNet. With
the exception of GUIs it is cross-platform. GUIs will be coming to Linux
Real Soon Now. There have been a couple of attempts but it isn't an easy
task given Gtk, Qt, and so forth.