Instantiating a class inherited from Forms

vzmon1 

I'm a little wary of replying here as you're touching on a topic that can blow out to be a very big discussion, and I'm also not keen to get involved in writing an application in PowerShell.

That said, here's some very basic observations from what you've dropped in your original post:

• You're mixing up inheritance and instantiation a bit too much;
• You shouldn't use both "using namespace" and the Reflection.Load()-style approaches together - choose one or the other (or the Add-Type approach used by the Microsoft Docs article you've referenced as a third alternative.)

In your example, you've defined a class named InputWindow which inherits from Form, but then within the constructor (which is broken in the example) you've created a local variable (named $form) and not done anything with the base class at all, making the inheritance quite unnecessary.

As for the mixing up of inheritance and instantiation, this is most evident in the comment about needing to include the ShowDialog() (and equivalents) in the constructor. While this can be done, it's not good practice to do so.

With your class constructor, all you're looking to do is define how things should look and behave when a new instance of the class is instantiated. So, what you're quite correct in including within the class constructor is the layout of all the elements and whatnot.

Stepping up one level to the class itself, you might then also have methods defined in your custom class that perhaps perform some kind of saving of data, or posting it via a REST web call to a service, or even just spit it out as a string (i.e. ToString() is commonly overridden in classes.)

The class itself is then consumed and used (through ::new() or New-Object, etc.) through the calling script/program/whatever, and it's from there that methods such as ShowDialog() should be called.

But as I mentioned above, I think most of this is not really going to help you as it doesn't sound like you need an expansive class. I'd say forget about inheritance and keep going as you have done already and define each new "window" as its own class while keeping the use of each (such as calling ShowDialog() or fetching data, etc.) back out in the calling script (i.e. your module is the "library" while your script is what makes use of the library.)

For posterity, here's what the official documentation says about classes, where I've bookmarked it some distance down where the article discusses inheritance with a good number of examples of the usage of the $this keyword.

• about Classes - PowerShell | Microsoft Docs

Cheers,

Lain