CommandDefinitions Property not available in C# but is available in VB.Net

[LukeDavenport]

Bit of a strange one this. The 'Item' property of the CommandDefinitions object isn't available when I'm in a C# project (see screenshot)

But it is available as usual when in a VB.Net project - see screenshot

I need to use this 'Item' property to access an Inventor command directly by name instead of having to loop through a couple of thousand commands to find the right one. 

I'm using Visual Studio 2015 and referencing the 2018 Inventor interop. Can anyone replicate this (just create two new empty projects and paste two lines in) or shed any light on why this property is missing?

Thanks,

Luke

[bradeneuropeArthur]

I see the same issue!!

[Anonymous]

.

[LukeDavenport]

Good, thank you for checking. Not sure how it is possible to expose a property in one .Net language, but not in another?

It appears you can see the other Read Only properties available for the CommandDefinitions object, just not 'Item'.

And its not just an intellisense problem, you can't compile if you try to go ahead and type it in anyway.

Anyone from Autodesk have any ideas?

[nmunro · Accepted solution]

C# does not use the Item property to access members of a collection. You should be able to access a specific ControlDefinition by using something like

InventorApplication.CommandManager.ControlDefintions["control_defintion_name"].Execute

Neil

[LukeDavenport]

Neil that's it! I must have missed that in C# 101. Slowly getting rid of my VB blinkers 🙂

Thanks