This project has moved and is read-only. For the latest updates, please go here.

Error handling

Jul 26, 2013 at 10:09 AM
How can I trap errors from command line, e.g. when the target dir is not writeable or .NET is not properly installed or not available?
Btw. why when I use fnr in a user startup script the black command line window flashes for a moment when fnr is processing my files?
Aug 25, 2013 at 7:34 AM
Edited Aug 25, 2013 at 7:35 AM

To trap errors from command line, you can write output of the fnr.exe to a file by using --logFile flag. See in documentation:

Then u can parse the file for any errors.

Another more involved way would be to get the code from codeplex and add any custom handling to code directly.

"fnr.exe" with "--cl" flag it is a command line application which opens a command prompt window to run.

One way you can hide it is by using hstart command mentioned here: