Alois Kraus


  Home  |   Contact  |   Syndication    |   Login
  133 Posts | 8 Stories | 368 Comments | 162 Trackbacks


Article Categories


Post Categories

Image Galleries


The new Enterprise Library for .NET 2.0 has disabled instrumentation by default. It is very reasonable to do this because in low trust scenarios you are not able to install Performance Counters, Windows Event Logs/Sources or update WMI schemas. The previous version had "configurable" instrumentation by some #ifdefs in the source code. To change instrumentation you had to recompile the whole library every time you wanted to target a different deployment and therefore trust scenario. This time the Enterprise Library team had more time to make it really configurable. The outcome is remarkable easy to use. You can enable/disable the following instrumentation settings:
  • Error logging of all Application Blocks to the Windows Event Log.
  • Performance Counter writes.
  • Firing of WMI Events.
Show more ...
posted on Wednesday, December 14, 2005 12:08 AM


# re: Enterprise Library for .NET 2.0 - Instrumentation 12/14/2005 11:21 AM Jannik Anker
Hi Alois,

Just wondering if you've considered doing posts like this one as articles? For those of us reading the main feed, long posts are unbelievably annoying. You could create an article and then create a post in which you refer to it. IMHO, that would be a much nicer solution...

# re: Enterprise Library for .NET 2.0 - Instrumentation 12/14/2005 7:07 PM Alois Kraus
Hello Jannink,

sorry to for the inconvinience. I have moved part of my article to the article section.


Alois Kraus

# re: Enterprise Library for .NET 2.0 - Instrumentation 12/15/2005 6:38 AM Jannik Anker
Looks great! Thanks ;-)

# re: Enterprise Library for .NET 2.0 - Instrumentation 5/17/2006 6:09 AM Jai
can anybody give me more information or give me some links to study about Enterprise Library for .NET 2.0 - Instrumentation?


# re: Enterprise Library for .NET 2.0 - Instrumentation 5/17/2006 5:40 PM Alois Kraus
Did you click on the Show more ... link? It will show you a much bigger article.

Alois Kraus

# re: Enterprise Library for .NET 2.0 - Instrumentation 10/13/2006 8:15 PM jay
I tried the code but it is not working...
Did anyone tried?

# re: Enterprise Library for .NET 2.0 - Instrumentation 10/15/2006 5:32 PM Alois Kraus
Hi Jay,

sorry I did forget to add the ProjectInstaller in the sample code. I have updated the article to make it work. When you do an installutil <yourexec> you should see some output like this:

>installutil ConsoleApplication4.exe

Microsoft (R) .NET Framework Installation utility Version 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.

Running a transacted installation.

Beginning the Install phase of the installation.
See the contents of the log file for the C:\Media\Blog\EntLib\Projects\EntlibWMI\EntlibWMI\bin\Debug\ConsoleApplication4
.exe assembly's progress.
The file is located at C:\Media\Blog\EntLib\Projects\EntlibWMI\EntlibWMI\bin\Debug\ConsoleApplication4.InstallLog.
Installing assembly 'C:\Media\Blog\EntLib\Projects\EntlibWMI\EntlibWMI\bin\Debug\ConsoleApplication4.exe'.
Affected parameters are:
logtoconsole =
assemblypath = C:\Media\Blog\EntLib\Projects\EntlibWMI\EntlibWMI\bin\Debug\ConsoleApplication4.exe
logfile = C:\Media\Blog\EntLib\Projects\EntlibWMI\EntlibWMI\bin\Debug\ConsoleApplication4.InstallLog
Installing WMI Schema: Started
Registering assembly: ConsoleApplication4_SN__Version_1.0.0.0
Ensuring that namespace exists: root\MicrosoftWmiNet
Ensuring that class exists: root\MicrosoftWmiNet:WMINET_Instrumentation
Ensuring that class exists: root\MicrosoftWmiNet:WMINET_InstrumentedNamespaces
Ensuring that class exists: root\MicrosoftWmiNet:WMINET_Naming

Post A Comment