MonitorWang v1.0.7

Rating: No reviews yet
Downloads: 88
Released: Feb 9, 2011
Updated: Feb 10, 2011 by jimbobdog
Dev status: Stable Help Icon

Recommended Download

Application MonitorWang_Binaries_v1.0.7.0
application, 5689K, uploaded Feb 9, 2011 - 52 downloads

Other Available Downloads

Source Code MonitorWang_Source_v1.0.7.0
source code, 9604K, uploaded Feb 9, 2011 - 36 downloads

Release Notes

What's new?

The focus for this release is a code restructure to allow you to build your custom implementations easier - the Core assembly has quite a lot of dependencies on third party assemblies and I want to structure this better so you could target the interface to implement and get the minimum of baggage. This came about because I am going to use MonitorWang as a server host for another project I am about to release and started to write an Activity and realised that I had to start pulling in references to Magnum, Castle etc.

Breaking Changes!
  • Moved the MonitorWang.Core.Interface folder into a dedicated assembly and split this into three "interface" assemblies to help manage the dependencies (magnum & castle) better. This allows you to reference MonitorWang.Core.Interfaces to build your implementations easier without having to pick up dependencies on Magnum or Castle. If you need to build implementations of either a HealthCheck publisher or Publisher Filter then reference the appropriate assembly (publisher = magnum, filter = castle).
    • Just reference the MonitorWang.Core.Interfaces assembly to implement new HealthChecks.
    • The binding, check and role castle.config files have all been modified to accomodate the type relocation.
    • It might be better to combine these into MonitorWang.Core.Interfaces.Publisher? Hmmm, I'll think about this some more.

Bug Fixes/Changes
  • HealthCheckBindingLoader had a fix to the "convention over configuration" logic used to create the name of the component from the binding configuration supplied. If your healthcheck configuration component had the word "config" in it as well as at the end it would fail to infer the correct component name.
  • Minor modification to the Growl result publisher to include the result Info field if not empty in the message text.

Reviews for this release

No reviews yet for this release.