I don't see any information in the logs for the initialization actions that I have added? even if they fail.

asked 21 Mar '12, 15:32

wildcatz's gravatar image

wildcatz
16141417
accept rate: 0%


Not all actions log messages to the installation log. Could you check if the <logMessage> action works to make sure it is not a bug? Which action are you executing?

link

answered 21 Mar '12, 16:19

juanjo's gravatar image

juanjo ♦♦
5.8k413
accept rate: 23%

It looks like it doesn't log anything when it fails! In this situation, I was trying to unpack a directory, a file and run a program. I had the paths wrong, but it just failed silently! Stranglely, when it succeeds, I do see it in the log. This isn't great!

(21 Mar '12, 20:25) wildcatz

Errors are usually not logged in the log because the installer throws a visible error. We do not log everything to the log because sometimes the developer do not want to show all that information to the end user (which have access to the log). If you need it for developing purposes, I would suggest you using the built-in debugger.

link

answered 30 Mar '12, 10:19

juanjo's gravatar image

juanjo ♦♦
5.8k413
accept rate: 23%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×26
×14
×4

Asked: 21 Mar '12, 15:32

Seen: 1,802 times

Last updated: 30 Mar '12, 10:20