-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
ScriptsToProcess not honored when Import-Module is passed -Version param #3738
Comments
@Matteo-T Thanks for your report! Could you check on latest PowerShell Core? |
My module does not work on PowerShell Core, so I'm not sure how that would help... I'm not sure I'll have time to create a dummy repro (i.e. a dummy module) that works on PowerShell Core any time soon, but if I have to... |
This repo is for PowerShell Core only. Please report regular Windows PowerShell issues on the uservoice website: https://windowsserver.uservoice.com/forums/301869-powershell |
@Matteo-T Please test after PowerShell Core Beta1 release (in the coming days). |
Sorry, I did not know this was for "Core" only. I was told to come here, but I guess I was told incorrectly. I'll try the UserVoice thing... |
@megamorf @Matteo-T for bugs that are almost certainly applicable to both editions of PowerShell, it's perfectly fine to file them here. I suspect that this one repros on Core 6 just fine, and given the importance of I'll build a basic repro on my box right now. |
Yup, totally repros on
|
Steps to reproduce
PowerShell -executionpolicy bypass
(observe that SqlServer.ps1, listed in the SqlServer.psd1 manifest file, is loaded during import)
Expected behavior
The SqlServer.ps1 script is loaded
Actual behavior
The SqlServer.ps1 script is NOT loaded
Environment data
The text was updated successfully, but these errors were encountered: