FesfPolicy logs messages to the Windows Event Log. Messages are logged for all unusual and anomalous events, including both fatal and non-fatal issues. Messages are logged to the Windows Logs\Application\FesfPolicy log.
The FESF Policy Service includes the capability to log messages to the console whenever errors are encountered in its interactions with the Policy DLL.
To make debugging and testing easier, the FESF Policy Service can be run interactively from the command line (instead of being installed and run as a Windows service). When you start FesfPolicy interactively, the command line to use is:
FesfPolicy [-debug | -DEBUG]
[logfile]
Starting FesfPolicy interactively and specifying one of the debug switches, will cause the Policy Service to output debug messages to the stderr (which is the command prompt window or the Visual Studio Output window if FesfPolicy is run from within Visual Studio).
The two forms of the "debug" switch are equivalent, except that when the uppercase version is used (that is "-DEBUG") FesfPolicy will issue a debug break point during startup.
When either of the "debug" switches are present, output can optionally be redirected to a file instead of to the console.
There is also a –SDEBUG option that, when FesfPolicy is run as a service, causes the service to conveniently issue a breakpoint during startup.
The FESF Policy Service may optionally be compiled to output debug data using OutputDebugString. See the source code for more information.