-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
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
Issue with new named functions as cmdlet #524
Comments
@deepjansari-rwe Thank you for contact us, and I apologize for the delayed response. New functions, aliases, etc. need to be added to the appropriate *ToExport array in safeguard-ps.psd1, for instance if you add a new function Get-MyNewFunctionName to
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am trying to add function by creating new file in src folder and then installing by install-local.ps1, however the PowerShell module does not identify the new function as cmdlet. I get the message - "The term 'Edit-SafeguardAssetAccountCustom' is not recognized as the name of a cmdlet, function, script file, or operable program."
I can see the new source files with function is placed at C:\Users\xxxxx\Documents\WindowsPowerShell\Modules\safeguard-ps\8.0.99999' after running install-local.ps1
Get-SafeguardCommand also does not list my new function.
However, when I modify existing function (assets.psm1 -> Edit-SafeguardAssetAccount) then it works fine, and module identify modified function with new parameters etc
I always run Remove-Module safeguard-ps and cleanup-local.ps1 before installing new module.
Is there any specific configuration need to be done to register new named functions as powershell cmdlet?
The text was updated successfully, but these errors were encountered: