> -----Original Message----- > From: Discussion of advanced .NET topics. [mailto:ADVANCED- > [EMAIL PROTECTED] On Behalf Of Kunle Odutola > > It seems JMX has no direct .NET counterpart as such. WMI is lower-level > and > vastly more complex but it seems to have the most overlap feature-wise. > I > haven't dug in to EIF much (and I'm avoiding unmanaged code options) > but, > I'm inclined to simply keep using our homegrown JMX-alike stuff. > Perhaps > also look into adding WMI adaptors.
Hi, A while ago I looked into EIF and the Logging and Instrumentation Block that used it. It appeared on the surface a little complicated for what it was trying to achieve, but before I got into it I found out about the Enterprise Library and how some people were calling it EIF v2. I don't imagine that's formally acknowledged anywhere, but it's true that the patterns folks behind the EntLib have taken over instrumentation and EIF won't be developed any further. All this rambling means that you might be safer staying away from EIF, and it might be worth investigating the logging application block in the EntLib: http://msdn.microsoft.com/library/?url=/library/en-us/dnpag2/html/EntLib2.as p (The EntLib is all managed, and you get all the source code too.) Hope this helps, Geoff =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
