We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PowerClippy.Format.ps1xml is an empty file and throws an error on import.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\powerclippy\1.0\powerclippy.psd1'. VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program Files\WindowsPowerShell\Modules\powerclippy\1.0\PowerClippy.Format.ps1xml'. import-module : Object reference not set to an instance of an object. At line:1 char:1 + import-module powerclippy -Verbose + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Import-Module], NullReferenceException + FullyQualifiedErrorId : FormatXmlUpdateException,Microsoft.PowerShell.Commands.ImportModuleCommand
The text was updated successfully, but these errors were encountered:
Same issue, ignores my attempts to Import-Module and throws similar exception
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\PowerClippy\PowerClippy.psd1'. VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program Files\WindowsPowerShell\Modules\PowerClippy\PowerClippy.Format.ps1xml'. Import-Module : Object reference not set to an instance of an object. At line:1 char:1 + Import-Module PowerClippy -Verbose + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Import-Module], NullReferenceException + FullyQualifiedErrorId : FormatXmlUpdateException,Microsoft.PowerShell.Commands.ImportModuleCommand
Sorry, something went wrong.
Commenting out the line that imports that ps1xml file resolves this.
No branches or pull requests
PowerClippy.Format.ps1xml is an empty file and throws an error on import.
The text was updated successfully, but these errors were encountered: