You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many WMI classes support methods. We should maybe just have a WMIMethodInvocation metaclass that takes the namespace, class, method name, and a property bag (key/value pairs) that would be the inputs to the method. The only problem with this approach is that the user needs to know all that info.
Alternatively, but would be noisy when listing, is to have dynamic instances returned that represent each method that can be called.
The text was updated successfully, but these errors were encountered:
Summary of the new feature / enhancement
Support:
Proposed technical implementation details (optional)
Many WMI classes support methods. We should maybe just have a
WMIMethodInvocation
metaclass that takes the namespace, class, method name, and a property bag (key/value pairs) that would be the inputs to the method. The only problem with this approach is that the user needs to know all that info.Alternatively, but would be noisy when listing, is to have dynamic instances returned that represent each method that can be called.
The text was updated successfully, but these errors were encountered: