-
Notifications
You must be signed in to change notification settings - Fork 22
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
How to import from path? #31
Comments
Try |
The README.md file is correct. I use this module often. You can pass a path to the |
If the readme is correct, and I'm importing the psd1 without errors, why don't the functions in the readme show up when I run 'get-command' for this module? |
Not sure. Works fine on all my machines, and first I'm hearing of this. It's all standard authoring and hasn't changed in years. Could be an issue with the PowerShell configuration on your machine, but I have no idea what that could be.
|
That's everything (and more; could of those files don't need to be in there and I'll remove). Run fuslogvw.exe from the .NET Framework SDK and see if there are binding errors. |
Fixes se[arate issue discovered in #31
Fixes se[arate issue discovered in #31
I've saved this module to a folder and am trying to import it from that folder. What is the correct file to reference to import it?
I've tried pointing to the PSM1 and it doesnt load
I've also tried importing the PSD1, and it loads but I dont see the commands referenced in the readme.
How can I import this from a specific folder that is not ever going to be in the
$PSModulePath
?The text was updated successfully, but these errors were encountered: