Forums | NoesisGUI

I would like to know if there is a way to perform the following tasks regarding the log file produced by Noesis SDK

1. Set the target output path of the log.
2. Control the content of the output log - determine the level of output (Info, Warning, Error etc..).

I tried the Logger::Mute method but it didn't affect the output file.

Hi Nir,

The target path of the log can be controlled using the config manager. It must be done before kernel initialization.
You cannot control the content of that file because its purpose is storing information that allows us tracking problems. Note that this behaviour is associated to the DLL included in the SDK. The standalone one (the one you are supposed to use in your application) does not generate log information because instrumentation is disabled.

What do you want to achieve? Let me understand better to help you.
Regards.

Thanks for the detailed reply.

I need to modify the output path of the log in order to place it with the rest of our application log files.
For now the content control is not that important, just something nice to have..

Regarding the different DLL you mentioned - Am I missing something important here ?
I'm currently linking against the Noesis.lib file that found under <SDK>\Lib.
For the runtime I copy the Noesis.dll, tbb.dll and tbbmalloc.dll directly from the <SDK>\Bin folder.
I don't have any other dll in the SDK i've got here (NoesisGUI-SDK-win-1.1.2.4603)..

Regarding the different DLL you mentioned - Am I missing something important here ?
I'm currently linking against the Noesis.lib file that found under <SDK>\Lib.
For the runtime I copy the Noesis.dll, tbb.dll and tbbmalloc.dll directly from the <SDK>\Bin folder.
I don't have any other dll in the SDK i've got here (NoesisGUI-SDK-win-1.1.2.4603)..

Your application should be linking against a runtime (there is a section for runtimes in the sticky downloads post). Binaries contained in the runtimes are smaller in size (many components are not included, for example the xaml importer, builder, etc) and faster (instrumentation and exceptions are disabled).

I am taking note about this to improve the documentation related to the SDK and Runtimes.