Standalone EXE

[unisoft]

Hi,

Anyway we can create a standalone Executable without the need of any DLL or file whatsoever ?

Regards

[Tom]

Use a different language.

This PDR is related to this problem. It's 16 years old.

http://www.alaska-software.com/scripts/ ... PDRID=4902

[Tom]

To be a little more serious. This is a problem by design. This design has some advantages - data driven applications and other things would be much more complicated without it. The disadvantage are the runtime DLLs you need to deliver. No way out. Maybe Xbase++ 5.0 (codename "cloud 7") supports this. It will be released in Q3 2027.

[bwolfsohn]

It will be released in Q3 2027.

You're such an optimist..

[Tom]

Okay, Q4 2027.

[rdonnay]

You could probably put the Alaska and eXpress++ runtime DLLs in a self-extracting ZIP EXE.

[unisoft]

Hi,

Just to make sure. thanks, so we have time till 2027, Q4 !!!

Regards

[Victorio]

Hi,

I also thought about it, because it is not nice, when user see tens od dll fiels in our directory and search exe file .

Only such an idea :
- put all dll to zip file
- when start application, first run "some" auxiliary exe module which "know" set of dlls which need main application (for example list can be in external ini file) and unzip those dlls
- and run main application.
- auxiliary module unzip dlls only first time, or only if he finds out some differences

This system can reduce dlls in directory, not unzip this, which ones not need

Sorry, if you mean something else altogether

[bwolfsohn]

Hi,

I also thought about it, because it is not nice, when user see tens of dll files in our directory and search exe file .

If your issue is the cline seeing these dll files, keep in mind the windows operating system, and most applications, call functions in dll files. the only difference is that these files are in a directory referenced by the path setting, (usually somewhere in the widows group of directories). You could move all the dll's into another directory under your mail directory, and the user wouldn't see them. You'd just need to change your code and possibly your installation routines to account for this.

[Tom]

You can't move the Xbase++-runtimes to another directory which is not the working directory of your app - or not included in the search path. You can't set the runtimes location in your app. This is a PDR aswell, maybe from 1996, but I'm not going to search it.