The ImportTester module has a module manifest, ImportTester.psd1. I've explicitly exported the function, but Export-ModuleMember doesn't have a Class parameter to export classes. In this test module, ImportTester, I've created an ImportTester class and a Test-Function function. But, Import-Module does not import PowerShell classes defined in the module. Import-Module would be a splendid tool to use to import classes. But, the introduction of side-by-side versioning in PowerShell 5.0 resurrected Import-Module and, in fact, made it your new best friend, because Import-Module has four version parameters that let you specify the version you want: ModuleVersion (minimum version), MaximumVersion, RequiredVersion, and FullyQualifiedName, which takes a ModuleSpecification object. With the advent of module auto-loading in PowerShell 3.0, Import-Module almost became obsolete. Let's start with the standard module import command, Import-Module. The Using statement is not yet documented, so this is a bit confusing. Instead, use the Using statement, introduced in PowerShell 5.0, which imports the module, including its classes, into the caller's session. To create different versions of a class, it's best to place the class in a module and use the versioning features of the module to create versions of your class.īut, to import the classes defined in a module into your session, you can't use Import-Module or even #Requires -Module. Tested On: Windows PowerShell 5.0, 5.1, 6.0.0.9, 6.0.0.10, PowerShell (Mac OS X) 6.0.0.9īeginning in Windows PowerShell 5.0, you can create PowerShell classes in scripts and modules.

Unable to find module info file