Browsing COM Objects
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
- mxtrinidad
- Posts: 399
- Last visit: Tue May 16, 2023 6:52 am
Re: Browsing COM Objects
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.
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
Bummer. For scripting I still often use the COM objects as some of them have no .NET equivalent.
Re: Browsing COM Objects
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.
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.
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.