**Programming newbie**

When a COM interface is available to a service, does one use this feature
when creating a cmdlet usually or would one find another way to interact?

I'm thinking about interacting with a service, but it is written in C.
There's a C API, but also a COM interface available. The COM interface
would definitely be useful with PowerShell scripts, but I'm thinking about
maybe giving a cmdlet a try.

Marco

Marco Shaw wrote:
> **Programming newbie**
>
> When a COM interface is available to a service, does one use this
> feature when creating a cmdlet usually or would one find another way
> to interact?
>
> I'm thinking about interacting with a service, but it is written in C.
> There's a C API, but also a COM interface available. The COM
> interface would definitely be useful with PowerShell scripts, but I'm
> thinking about maybe giving a cmdlet a try.
>
> Marco

I'd go with COM , this gives a smoother experience across scripting
languages, asn WSH does COM too,
i'm working on a similar project, a Query-IndexServer cmdlet that depends on
COM Interfaces from ADODB and IXSSO.Query and IXSSO.Util,
using tlbimp to generate an interop assembly is pretty straight forward.
I'd be happy to try and answer any questions you have, maybe we can document
our experiences with the SDK as programing newbies.

regards
Joris

>i'm working on a similar project, a Query-IndexServer cmdlet that depends
>on
>COM Interfaces from ADODB and IXSSO.Query and IXSSO.Util,
>using tlbimp to generate an interop assembly is pretty straight forward.

Have a blog?

Marco Shaw wrote:
>> i'm working on a similar project, a Query-IndexServer cmdlet that
>> depends on
>> COM Interfaces from ADODB and IXSSO.Query and IXSSO.Util,
>> using tlbimp to generate an interop assembly is pretty straight
>> forward.
>
> Have a blog?

It's more like a brain-cache http://whizzrd.spaces.live.com