How to Report a Bug or other Issue

Several people have contributed to enhance the quality of .NETZ. If you encounter a problem with .NETZ that is not described anywhere in this web site, please report it.

Before you report a bug make sure that:

1. You have the latest version of the .NETZ binary.

2. Make sure you understood the latest .NETZ limitations.

3. Make sure you have read the latest .NETZ help contents on this web site. The help is updated constantly. Most advanced issues, such as, .NET resource mismatch, can be handled with a simple re-compilation, and this is explained in help.

4. Check out known issues. If the issue you want to report is found there, then do not report it.

5. Chek out the FAQs section.

6. Read this document completely.

If the answer cannot be found above and errors persist, then please report it (to this email address). To make sure that the bug can properly located and reproduced please go through all the following check list steps.

If you get a compilation error when you run .NETZ to compress and EXE or DLLs, then:

1. Run .NETZ with the failed command-line plus the -v option (before the other options). E.g. if you run netz -z app.exe then re-run it as netz -v -z app.exe.

2. Send the generated error.txt file (if any) to the email address shown by .NETZ (found also at support).

3. Include also the output of netz -! command, if it is not generated automatically during the error. The -v option includes also the output of the -! command.

4. Include a screenshot of the console or copy the console text.

5. Errors that you get when you are using modified start templates or while developing custom compression providers are NOT supported. The netz -! command reports the fingerprints of the used templates to avoid any misunderstanding. If you are using a compression provider named other than defcomp.dll, e.g. net20comp.dll, then run netz -r net20comp.dll -! and send the printed output.

If you get an error when you run a .NETZ packed (compressed) application, then:

1. Include a screenshot of the error. .NETZ error messages shown in this case are very informative.

2. If possible send the source code (or the EXE) of the program that fails, or preferably a small test program that demonstrates the failure.

3. Once more, check the advanced help sections. Some warnings, such as 1004 and 1005 are explained in the help.

Optionally, in both cases include a suggestion what you think causes the error and how do you think it could be corrected.

Credits for the reported bugs and suggestions are listed publicly in this web site if you provide your full name.

Please report all bugs or other issues in the following email address.