Question: How does EurekaLog.NET work?
Answer: EurekaLog.NET perfectly integrates itself with Visual Studio's IDE and builds (with the normal compile command) your applications with the new capability to intercept every exception and trace a detailed and customizable log of every code point executed between the application's start and the point where an exception is raised (showing address, module, unit, class, method, line number, column and much more).

Question: What new files I need to deploy with my project after I compile it with EurekaLog.NET?
Answer: EurekaLog.dll (a new dll automatically added to your project dependences) and the project .PDB file (optional but needed to can obtain a call-stack with the line numbers).

Question: How much does EurekaLog.NET increase compiled file size?
Answer: EurekaLog.NET increases the compiled file size by about 16KBytes (and add a new EurekaLog.dll file of about 500KBytes).

Question: Is EurekaLog.NET compatible with the automatic build systems, as FinalBuilder, Automated Build Studio and others?
Answer: Yes, it is full compatible with any automatic build system, you need simple build the Visual Studio project or solution and EurekaLog.NET will be automatically added to it.

Question: Can EurekaLog.NET decrease an application's performance?
Answer: Definitely NOT, because it works only when an exception is raised.

Question: Is EurekaLog.NET compatible with exe compression/protection software?
Answer: Yes, EurekaLog.NET is FULLY compatible with exe compression/protection software, so you can use those tools without any restrictions.

Question: Does EurekaLog.NET work with DLLs?
Answer: Yes it does.

Question: What does EurekaLog.NET do when it intercepts an error?
Answer: It displays a window to communicate the error in a graphic (GUI) application, it shows a text in a Console application and shows an HTML document in a Web application.

Question: What is the log file's extension?
Answer: It is *.EL (EurekaLog.NET file).

Question: Does EurekaLog.NET intercept every type of exception-based error?
Answer: Yes it does. EurekaLog.NET is able to intercept every type of exception-based error, Thread, Console and Internet Web exceptions included.

Question: How many errors can EurekaLog.NET store in the file log?
Answer: There are no limits.

Question: When there are errors already verified and saved in the log file, is it possible to avoid further savings?
Answer: Yes it is. You must set the "Do not save duplicate errors" option in the "Exceptions Log Options..." menu (see here).