When command line is empty an exception is not caught

Bug #643524 reported by Manuel de la Peña
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
WADL Sharp
Fix Committed
High
Manuel de la Peña

Bug Description

I tried to merge this, but stumbled across an error

When invoking wadl-sharp executable without any parameter, it gives me an error instead of a Help menu as I can see in the file Program.cs in WadlConsole

The error I get is

Unhandled Exception: System.ArgumentException: An empty file name is not valid.
  at System.IO.FileSystemInfo.CheckPath (System.String path) [0x00000] in <filename unknown>:0
  at System.IO.FileInfo..ctor (System.String fileName) [0x00000] in <filename unknown>:0
  at (wrapper remoting-invoke-with-check) System.IO.FileInfo:.ctor (string)
  at LpNet.WadlSharp.Common.WadlConverter.Convert (System.String inputFileName, System.String outputFileName, System.String rootNamespace) [0x00000] in <filename unknown>:0
  at Wadl.Program.GenerateCode (System.String inputFileName, System.String outputFileName, System.String rootNamespace) [0x00000] in <filename unknown>:0
  at Wadl.Program.Main (System.String[] args) [0x00000] in <filename unknown>:0

Related branches

Changed in wadlsharp:
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Manuel de la Pena (mandel)
Changed in wadlsharp:
status: Confirmed → In Progress
Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :
Changed in wadlsharp:
status: In Progress → Fix Committed
milestone: none → 0.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.