Exceptions not captured in Boxstarter.log about boxstarter HOT 3 CLOSED

It should definitely be logging errors. Thats certainly the intent at least. A few questions:

1. Do you see log files in c:\vagrant?
2. Have you checked the the former log directory? $boxstarter.log was not intended to be changed. Its absolutely a sensible thing to want but its not at all tested and its possible changing it in the package may not be applied at the right scope.
3. Are you launching the script locally on the vm where it is running? If not, its possible the errors are in the log on the host.

from boxstarter.

Well, it seems to be working today 😝 I was searching the log for the words "exception" and "error". Maybe the exception message didn't contain those. It seems to log only the exception message and no stack trace, exception type, etc. So that may have been my confusion point.

Feel free to close this, and if I can repro an actual bug I'll post a zip of a repro case. Thanks!

Btw, setting $boxstarter.log seemed to work a treat except that it didn't persist between reboots. I had to set it at the top of every script I called from Install-BoxstarterPackage to try to make up for this, and some of the output in between may be getting lost at the old log location. I was launching from inside the VM.

from boxstarter.

Yup. Thats a duplicate of #18. Need to make the log file configurable.

from boxstarter.