[shimgen] no error written to standard error on error

[ghost]

new with 0.9.9, when you launch a process to install a chocolatey package and an error occurs (my example is 'elasticsearch not installed. The package was not found with the source(s) listed.'), it no longer writes anything to standard error.

It used to do this properly before 0.9.8. Is it on purpose that in 0.9.9 you need to parse standard output in order to detect an error?

[ferventcoder]

Interesting. I would think log4net would do that properly.

[ferventcoder]

Can you expand on this a bit more?

[ferventcoder]

So the exit code should be non-zero. That's a start. The other side of this is that it should be writing to stderr for things that are logged as errors.

[ghost]

In a C# application, I launch a new process that uses chocolatey to install a package and capture StandardOutput and StandardError.
If anything was written to StandardError, it would detect and log an error, blocking the program from continuing.
Previous to 0.9.9, this was working. Now with 0.9.9, this no longer works.

[ferventcoder]

Dumb question, are you calling the shim?

[ghost]

hrm. I might be. I'm calling cinst.exe

[ferventcoder]

This isn't new to choco 0.9.9 then :)

[ferventcoder]

What version of choco did you have in place before?

[ghost]

0.9.8.33.

[ferventcoder]

the shims there would have been wrong as well though.

[ghost]

let me double check this. I hope I haven't been wasting your time....

On Tue, Mar 3, 2015 at 2:13 PM, Rob Reynolds notifications@github.com
wrote:

the shims there would have been wrong as well though.

—
Reply to this email directly or view it on GitHub
#142 (comment).

[ferventcoder]

I wonder if there was something else in the path then...

[ferventcoder]

No it's good. The shims should properly output stderr to stderr.