EurekaLog does not follow the options settings

[jaym]

Hi Fabio

I am trying the 6.0.16 RC 4 Trial.

These are the settings in EurekaLog Options dialog.

Email & Web send tab
Send Mode: Email Client
Addresses: entered my valid email address
Subject and Mesage text boxes: filled with some text

Send Options tab
All the check boxes (checked)
Attach files (application.config.xml)
Zip password (assigned)

Log file tab
Save Log file (checked)
Number of errors to save (32)
Add 'Computer Name' in Log file name (checked)
Save Modules and Processes sections (checked)

Exception Dialogs tab
Dialog type: EurekaLog
Foreground Tab: Call-Stack
All the check boxes (checked)

================================================== ========================
I was expecting to see EurekaLog full dialog displaying the Call-Stack tab.
What I am getting is just a message box with

Error occured
The application has encountered a problem. We are sorry.....
Actual error (in my case, InvalidArgument=Value of '1' is not valid 'index'.)

To see what data the error report contains, click here (link)

An OK Button.
================================================== ========================


Clicking the OK buttons closes the message box. It does not send email, I was expecting to see my email client start with the attached files (screenshot, bugreport.zip (which I do not like the name) and my application.config.xml file.

I have 3 problems.
(1) Wrong dialog displayed
(2) Email client not started to send the email with attachments.
(3) Just changing the Eurekalog options does not flag that the Project is dirty and needs rebuild. You have to make a change somewhere in any other files of the project to apply the changed Eurekalog options. (the eof file is not a part of the project file as in Delphi).


Cheers

Jay

[admin]

Hi Jay,
I have 3 problems.
(1) Wrong dialog displayed
(2) Email client not started to send the email with attachments.
(3) Just changing the Eurekalog options does not flag that the Project is dirty and needs rebuild. You have to make a change somewhere in any other files of the project to apply the changed Eurekalog options. (the eof file is not a part of the project file as in Delphi).

I cannot reproduce the points 1 and 2.
I have just reproduced and fixed the point 3 (what do you mean with: "the eof file is not a part of the project file as in Delphi" ?).

Can you create and send to me a little source demo able to reproduce the points 1 and 2 please? :)

[jaym]

Hi Fabio

I had couple of projects built using EurekaLog 6.15 Trial.

When I installed 6.16 RC4 Trial I had set all my EL options set as stated in my previous post. On building the existing projects that were created when 6.15 was installed the behaviour was exactly as I stated in my post.

Then I created a new project with 6.16 the problems 1 and 2 have gone.

With the existing projects I removed (deleted) the projectname.edata and projectname.eof files.
I then opened the EurekaLog options dialog and saved the options, the projectname.edata and projectname.eof were recreated when I built the project and it is working fine. I get the EurekaLog dialog opened with call-stack tab displayed.

It looks like that removing (deleting) the .edata and .eof files have fixed the problem.

I am still after the option of having my own zip file name instead of BugReport.zip. In the Delphi/BCB version I can change the file name (in ExceptionLog.pas the return value of function TmpZIPFileName) as I get the source code, but for the VS version I would like to have an option where I can have a different zip file names for different projects. You understand what I am after.

Cheers

Jay

P.S. I will keep using the trial until I am satisfied and then buy. EL is a great tool as I am using in all my Delphi projects since last 3+ years.

[admin]

Hi Jay,

I have just released EurekaLog .NET 6.0.16 RC 5.

I think to have also fixed your previous 1 and 2 points.

For the BugReport.zip file name I'll working on (is a promise). :)

In the mean time can you test this new release and tell back to me your results, please?

[jaym]

Hi Fabio

Everytime I build my application and run it, my Zone Alarm Smart Defence pops up. (please see the attached image)

The ecore.exe (starts and gets registered from temp folder) and for this reason Zone Alarm complains. If the user clicks Deny button, what will happen.

With the original EurekalogCore.dll I did not this problem with Zone Alarm.

My question are

My applications run on a Terminal Server (using Remote Desktop)

Say for example, my client is using my current application built using EurekaLog (say 6.16).
Then 6 or 12 months later I deploy a new application using your more powerful version (say 7.2). Both these applications will run at the same time.

What will happen to the ecore.exe which gets extracted from the resource of Eurekalog.dll ?

Will there be a problem in this situation ?

Do we want to deploy ecore.exe to System folder, (with proper version info details in it) with the every new application deployment ?

Later installations of other applications will check the version and only deploy a newer version.

More to come as I think and work on EL.

Cheers

Jay

[admin]

Hi Jay,

Hi Fabio

Everytime I build my application and run it, my Zone Alarm Smart Defence pops up. (please see the attached image)

The ecore.exe (starts and gets registered from temp folder) and for this reason Zone Alarm complains. If the user clicks Deny button, what will happen.

With the original EurekalogCore.dll I did not this problem with Zone Alarm.


I think to have fixed it in the last 6.0.16 RC 6 (I cannot test it because on my PC Zone Alarm do not shows any pop-up).

Can you test it and tell back to me your results, please?


My question are

My applications run on a Terminal Server (using Remote Desktop)

Say for example, my client is using my current application built using EurekaLog (say 6.16).
Then 6 or 12 months later I deploy a new application using your more powerful version (say 7.2). Both these applications will run at the same time.

What will happen to the ecore.exe which gets extracted from the resource of Eurekalog.dll ?

Will there be a problem in this situation ?

Do we want to deploy ecore.exe to System folder, (with proper version info details in it) with the every new application deployment ?

Later installations of other applications will check the version and only deploy a newer version.

More to come as I think and work on EL.

Cheers

Jay

The our internal mechanism automatically handle different versions on different processes, so don't worry about it! :)

PS: if the problem persists, then can you tell me what are all the action to execute to can reproduce it, please (also sending to me a project source demo and the list of the Zone Alarm settings to change)?