Page 1 of 1

Browsing COM Objects

Posted: Tue Mar 27, 2018 3:24 am
by shocko
Does the powershell studio support browsing COM objects?

Re: Browsing COM Objects

Posted: Tue Mar 27, 2018 3:36 am
by mxtrinidad
No that I know. In the case of Office objects, there are .NET wrapper the tackle MS Office product:
For example:
"Microsoft.Office.InterOp.Excel"

But, MS Office need to be installed and remember that there are both 32bit and 64bit versions.

Com Objects are old technology replaced by .NET. Better off looking at some community contribution on this topic.
:)

Re: Browsing COM Objects

Posted: Wed Apr 11, 2018 6:47 am
by shocko
Bummer. For scripting I still often use the COM objects as some of them have no .NET equivalent.

Re: Browsing COM Objects

Posted: Wed Apr 11, 2018 7:15 am
by davidc
PowerShell Studio's PrimalSense will provide the names of COM Objects when using the New-Object cmdlet.

You can try the following:

Set a breakpoint after you create the COM object and store it into a variable. Debug the script and when it hits the breakpoint, PowerShell Studio will collect the state information (after the variables are populated in the Variables panel). Then stop debugging and see if you get the necessary properties and methods for the variable.