TurboFloat Server log file notification level and command line

Hi guys!

I know couple months ago a change was made in TFS so that the log notification level would be respected in the command line window. I was uncomfortable about that change but said nothing about it.

Now we had a small problem this morning with a new setup because of that.

By default we package a config file with level="none" so that we do not have to bother modifying the config file when installing to provide a valid path for the log file. All right.

Then our setup application calls TFS to register and install on the server. We catch errors to inform the user if TFS failed to register properly. All right.

Then problem was that the user was installing on a VM and the TF key was not allowing that. (This was fixed quickly.)

The real problem is that the setup program never catch the key registration problem. Why? Well, because the command line was returning nothing because the log file level was "none".

I can fix my current setup to have proper leg level by default. But I would have much more prefer that the log level stayed a log level and that the command line always returns what it has to return. Usually we only use command line for administrative purposes or debugging. As far as I'm concerned, command line should always be level="notification".

I would suggest to add a new command line parameter so that we can set the verbose level for the current action/session.

TurboFloatServer.exe -level="warning" -a ...

That was even if the log file level="none" the command line would actually return something when asked to do so.

I've seen comment about a coming release with new features. I'm eager to see that!

Best regards,Alexandre Leclerc