Releases: yarseyah/sentinel
Sentinel 0.14.1
Sentinel 0.14.0
Implemented requested feature to limit number of log entries displayed by the logging window.
Limit may be enabled in Preferences and number of entries defined.
Addressed the lack of persistence of user preferences between sessions. Settings made on the General and Commands tab are saved on exit and reloaded.
Sentinel 0.13.6.0
Minor update to implement experimental internal commands (as suggested in #15).
Within the preferences dialog, a new tab for "Commands" exists, there is currently 1 command implemented to clear the log.
When enabled, if a message description matches exactly the string defined for the command, then it will clear the log history and display window. Default value for the text is #!Clear
. It does not matter what logging level this message is sent at.
NOTE: at extremely high frequencies of clearing the log, the WPF renderer may throw IndexOutOfRange exceptions, use the command at frequencies of greater than 200ms apart.
Sentinel 0.13.5.0
Sentinel 0.13.4.0
Quick update to 0.13.3.0 because update mechanism (which can now look on GitHub) was not working correctly due to not releasing an internal update mutex.
Sentinel 0.13.3.0
Due to changes in SSL/TLS 1.0 support at GitHub, the auto-update mechanism was not able to make connections when looking for updates.
- The base application now uses
.NET Framework 4.6.1
as the base run-time (up from 4.5)
Whilst there were other techniques that could establish a connection on older versions, I've decided that the .NET Standard 2.0 and .NET Framework 4.6.1 parity is a useful addition which will reduce version conflicts in 3rd party libraries.
Sentinel 0.13.2.0
Bug Fixes
Addresses unnecessary dependency on Segio UI font which resulted in a crash if not found. #1
New features
- Added a 'Context' column (can be toggled on/off)
Uses a named property for of the message to represent context. An example scenario of this is within unit-testing. Messages can be associated to the context of the named unit test. Example further below for MSTest2.
Currently only nLog is supported. It defaults to using a named property of "UnitTest", but this can be changed in preferences.
The client (sender) needs to be configured (e.g. in the nlog.config
) that the Mapped Diagnostics Context (Mdc) should be sent in the message payload, such as:
<target name="viewer"
xsi:type="NLogViewer"
includeSourceInfo="true"
includeMdc="true"
address="udp://127.0.0.1:9999" />
Example of context associated unit-tests
Before each unit-test method, in the TestInitialize
, set the context.
[TestInitialize]
public void TestInitialize()
{
var test = $"{TestContext.FullyQualifiedTestClassName}.{TestContext.TestName}";
MappedDiagnosticsContext.Set("UnitTest", test);
Log.Info($"***** Started test '{test}' *****");
}
And end it by removing the context:
[TestCleanup]
public void TestCleanup()
{
var test = $"{TestContext.FullyQualifiedTestClassName}.{TestContext.TestName}";
Log.Info($"***** Started ended '{test}' *****");
MappedDiagnosticsContext.Remove("UnitTest");
}
Sentinel 0.13.1.0
Fixed defect where log4net sessions were not correctly loading (when "Save Session" was used).
Sentinel 0.13.0.0
Only change is the use of the ClickOnce replacement using Squirrel.Windows.
To disable the auto-update functionality, pass --inhibit-upgrade
on the command line. Further options to control the update functionality will be added soon. Add suggestions or submit Pull-Requests 😄
For installing, you only need the EXE file. In future, the application will automatically find new releases and (after prompting) install them. It does this by using the RELEASES and *.nupkg files (see Squirrel.Windows for more details).
Sentinel 0.12.4.0
Last CodePlex release (non-ClickOnce) transferred over to GitHub
Note, ClickOnce installer will be replaced in future release