#20 CLI based generation not working

[Markus KARG]

I am using chmProcessor 1.6.3 on Win 7 Pro SP1 64 Bit.

Note: In GUI mode all is working well (despite the bugs already noted in this tracker)!

But when using CLI mode, it does not work at all.

[A] When using /g /q /y /e it shows a stack trace:
Invalid character in given encoding. Line 1, Position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
...
at System.Xml.XmlDocument.Load(String filename)
at ChmProcessorLib.ChmProject.Open(String filePath)
at ChmProcessor.CommandLineMode.GenerateOnConsole()

[B] When uisng /g /q /y /e /l1 it does the same as without /l1.

[C] When using /g /q /y /e /l2 it prints the help screen, but does NOT show the stack trace, but also does NOT produce a CHM.

[D] When using /g /q /y /e /l3 it does the same as with /l2.

As the same .doc file is working in GUI mode, it seems to be independent of the .doc file I am using.

[Antonio Fco. Bennasar Obrador]

Ups. Right now, the command line was expecting only a .WHC file (a ChmProcessor project file) on the command line, not a Word/HTML file. Going to change it for the 1.7.1 version. Thank you.

[Antonio Fco. Bennasar Obrador]

Will be fixed in 1.7.1