CommandLineException should have the command and args in its message #479

suwatch opened this Issue Mar 21, 2013 · 1 comment


None yet
3 participants

suwatch commented Mar 21, 2013

This would help pinpoint the issue w/o looking at dump.

@ghost ghost assigned pranavkm Mar 21, 2013

@pranavkm pranavkm closed this Mar 22, 2013

@ghost ghost assigned fashaikh Mar 26, 2013


fashaikh commented Apr 2, 2013

Verified on deploying from
the command line arguments are present in trace.xml as:

<step title="Error occurred" date="04/02 20:57:30" type="error" text="Unhandled Exception: System.Exception: Something went wrong&#xD;&#xA;   at CommandLine2.Main(String[] args) in c:\Users\fashaikh\Documents\Visual Studio 2012\Projects\TestCommandLineArguments\TestCommandLineArguments\Program.cs:line 17&#xD;&#xA;d:\projectkudu\kudu\Kudu.Services.Web\bin\scripts\starter.cmd TestCommandLineArguments.exe l;lkkl;k 234324 sdffc 6453 lkjlkcjvkl jjkljl 6546 m,nvm,cxnv,mnv,n ;';l';'; hjhj" stackTrace="   at Kudu.Core.Infrastructure.Executable.Execute(ITracer tracer, Func`2 onWriteOutput, Func`2 onWriteError, Encoding encoding, String arguments, Object[] args) in d:\projectkudu\kudu\Kudu.Core\Infrastructure\Executable.cs:line 374&#xD;&#xA;   at Kudu.Core.Infrastructure.Executable.ExecuteWithProgressWriter(ILogger logger, ITracer tracer, String arguments, Object[] args) in d:\projectkudu\kudu\Kudu.Core\Infrastructure\Executable.cs:line 293&#xD;&#xA;   at Kudu.Core.Deployment.Generator.ExternalCommandBuilder.RunCommand(DeploymentContext context, String command) in d:\projectkudu\kudu\Kudu.Core\Deployment\Generator\ExternalCommandBuilder.cs:line 65" elapsed="0" />
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment