Root > Integral parts > Project types (profiles)

Project types (profiles)

Previous pageReturn to chapter overviewNext page   

What is a "project type"?

"Project type" is just a template of EurekaLog's settings. You can specify project type for your project in EurekaLog's project options when adding EurekaLog to your project:



Project type (profile) selector in EurekaLog project options


When you select a profile - some settings of your project will be changed accordingly to selected project's type. See list of types below for more information.


"Supported project type" means that EurekaLog has predefined template "out-of-the-box".
"Unsupported project type" means that EurekaLog doesn't have a template for this kind of project. You need setup it manually.
"Custom project type" means that template was defined by developer (you).



Supported profiles

EurekaLog supports the following types of projects "out-of-the-box":


VCL GUI application - this is for projects with Forms unit.
FireMonkey application - this is for projects with FMX.Forms unit.
Control Panel application - this is for projects with CplApplet unit. There is a second option for projects with both Forms and CplApplet units.
NT Service application - this is for projects with SvcMgr unit.
CGI application - this is for projects with CGIApp unit.
ISAPI application - this is for projects with ISAPIApp unit.
IntraWeb application - this is for projects with IntraWeb unit.
Console application - this is for console projects.
DLL - this is for DLL projects, which are used in EurekaLog-enabled application.
Standalone DLL - this is for the DLL projects, which are used in non-EurekaLog enabled application.
Package - this is for package projects.
CLX application - this is for projects with QForms unit.



Unsupported profiles

For other types of projects you need to select options manually. Just select "Custom settings / unsupported type" value and set the other necessary settings. You also may need to write some code. See unsupported projects for more information.



Custom profiles

You can set EurekaLog options and export them to external .eof file (see also: Working with settings). Custom profiles (i.e. saved in .eof files) will appear at the end of "Project types" combo-box, provided it was saved into default location (i.e. you did not change folder in "Export settings" dialog):



"Project type" option shows two custom .eof files


Note: The path for loading custom profiles is %AppData%\Neos Eureka S.r.l\EurekaLog\Profiles\ (e.g. like C:\Users\UserName\AppData\Roaming\Neos Eureka S.r.l\EurekaLog\Profiles\).


Selecting any of "custom" values from "Project type" option will load settings from the corresponding .eof file into your project. All settings in your project will be replaced with values from .eof file. Using custom profiles allows you to quickly switch between settings in few mouse clicks.



See also:

Send feedback... Build date: 2022-03-28
Last edited: 2022-01-14
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: