Comments on: Writing C# applications to do complex monitoring with SCOM

By: Tim

Tim — Tue, 29 Sep 2009 00:31:55 +0000

Nice work. I prefer C# as everything is exposed and only requires the .net framework which is installed more often then powershell on our servers.

By: Hu Bo

Hu Bo — Mon, 21 Sep 2009 08:40:12 +0000

I would bet it is much easier to use powershell

[int]([object[]](dir *.xml)).length

By: Tim

Tim — Tue, 07 Jul 2009 13:56:53 +0000

I would bet that will work as well. I figured there was a way to do it in VB as well. Good Stuff

Thanks

By: marcus

marcus — Thu, 02 Jul 2009 12:55:25 +0000

hey tim – great blog & info. i don’t have a directory with enough files to process but was curious if you would have achieved better results digging through with wmi – such as:

sComputer = “.”
Set oWMIService = GetObject(“winmgmts:” _
& “{impersonationLevel=impersonate}!\\” & sComputer & “\root\cimv2″)

Set cFiles = oWMIService.ExecQuery(“Select * from CIM_DataFile where Drive = ‘c:’ and Path = ‘\\temp\\’ and Extension = ‘xml’”)

i = 0
For Each oFile in cFiles
Wscript.Echo oFile.Name
i = i + 1
Next

WScript.Echo “Count: ” & i

By: Tim

Tim — Sun, 21 Jun 2009 14:52:17 +0000

Not true. I am copying the C# application down to the client that I running it on. They both are running on the client. The reason it is so much quicker is that in the vbscirpt I am touching every file. In the c# program I am just hitting the directory and using the System.IO.Directory.GetFiles method on the directory. This is much more efficient as it just hits the directory. Vbscrpt doesn’t have this method, but the real point was to show how to you can write c# apps and leverage them in SCOM.

By: Tao

Tao — Sun, 21 Jun 2009 10:50:21 +0000

the vbscript you used was filtering the result on the client side. of cause it is going to be slow. and the code in C# uses server side filtering, that’s why it’s much quicker.