Navigation:  Programming Cookbook > Creating Console Applications >

Deploying Console Applications

Previous pageReturn to chapter overviewNext page

An important difference between GUI and Console applications is the executable stub file that is used. Console applications must use ConsoleStub rather than EmptyStub. If the latter is used then Windows will not recognise the executable as a console application, and will not create or connect to a console window for the application. In addition the standard I/O streams will not be initialised correctly. The Lagoon Deployment Wizard should automatically select the correct stub file.

It is recommended that when first deploying a console application the default options be retained (although it should be safe to strip deprecated methods too).

It goes without saying that console applications are not intended to support graphical user interfaces. You can use MessageBox to display notifications, but apart from that Dolphin's MVP sub-system is not correctly initialized in console applications, and should not be used. It is worth checking package pre-requisites to be sure that GUI classes have not inadvertently been used. The deployment manifest can also be checked using the Executable Browser to be verify that all MVP related classes are stripped from the console executable. If they are, then the executable will be significantly smaller, and small utilities should come in well under 0.5Mb, the minimum size being around 370Kb.

Once an application has been deployed it can be best tested by invoking it directly from the command line.