Distributing In-House Engineering Code?

caswelmo asks: "My company has recently moved from Solaris workstations to Windows workstations (Ohhh, the humanity). As an engineering focused company, we use our computers to run many in-house (command line) codes to analyze and design our products. We currently use NAS storage to store everything and use batch files and init scripts to run the correct codes over the network. This makes sure everyone is running the latest version. This also stinks. I know this isn't an original problem, so what are some other solutions for rolling out lots of simple codes like this?"

Comments

Windows App

[Zapper]

Well now that you're using Windows, you can hire some graduate to write an enormous, confusing GUI in like, VB or C# or whatever the latest incompatibility from MS is that pulls the the latest algorithms from a central server. (how's that for a run on sentence!)
That way you can use all the latest buzzwords like "live-update" and umm, "client/server" and umm, "network" and whatever buzzword pack that comes with .NET.
Oh, oh, wait... you could use MS Access with a custom interface and have all the codes stored in a database. Mmmmm, database.