13 May, 2025

"Invalid EurekaLog configuration found" error

Users of recent EurekaLog versions could receive the "Invalid EurekaLog configuration found" error message when they run their EurekaLog-enabled applications. The message looks like this:
Invalid EurekaLog configuration found.

Exception from the following module:
full-file-name-to-your-EXE-or-DLL
was catched in the following module:
full-file-name-to-your-DLL-or-EXE
Both modules have EurekaLog enabled, but EurekaLog code is not shared.

This is essentially the same error as:
- "Can''t assign a TFont to a TFont";
- "Invalid class typecast";
- reInvalidCast;
- "Run-time error 10".
etc.

Possible solutions:
- Do not allow exceptions from one module escape into another (recommended)
- Compile DLLs with Lightweight DLL profile, so your DLL will not have EurekaLog's code
- Compile EXE and DLL with run-time packages, so EXE and DLL will share EurekaLog's code

See our help for more information:
https://www.eurekalog.com/help/eurekalog/dll_using_eurekalog.php

11 May, 2025

Using EurekaLog with GMail (Google Mail) after May 1, 2025 and after May 14, 2025

Google has announced that it’s disabling the less secure apps, third-party apps, or devices that ask you to sign in to your Google Account with your username and password on Google Workspace accounts from May 1st or May 14, 2025:
Starting March 14, 2025, you and your users must use OAuth with third-party apps to access Gmail, Google Calendar, and Google Contacts.You will no longer use a password for access (with the exception of app passwords). Google is turning off access to less secure apps—non-Google apps that can access Google Accounts with a username and password (basic authentication).