Repository navigation
Incorrect module path when using .NET interactive #463
Copy link
Copy link
Closed
Labels
Milestone
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
Steps to reproduce
When running Install/Update-PSResource in a .NET interactive notebook the installation path is incorrectly set as Documents\WindowsPowerShell, even though powershell core is being used
Notebook code (.dib file)
#!pwsh
$PSVersionTable
Install-PSResource -Name 'Az.Accounts' -Repository PSGallery -Scope CurrentUser -Verbose -TrustRepository
Output:
Name Value
---- -----
PSVersion 7.1.3
PSEdition Core
GitCommitId 7.1.3
OS Microsoft Windows 10.0.19042
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
VERBOSE: All paths to search: 'C:\Users\henry.buckle\Documents\WindowsPowerShell\Modules'
VERBOSE: All paths to search: 'C:\Users\henry.buckle\Documents\WindowsPowerShell\Scripts'
VERBOSE: Performing the operation "Install-PSResource" on target "package to install: 'Az.Accounts'".
VERBOSE: Parameters passed in >>> Name: 'Az.Accounts'; Version: ''; Prerelease: 'False'; Repository: 'PSGallery'; AcceptLicense: 'False'; Quiet: 'False'; Reinstall: 'False'; TrustRepository: 'True'; NoClobber: 'False';
VERBOSE: Attempting to search for packages in 'PSGallery'
VERBOSE: Untrusted repository accepted as trusted source.
VERBOSE: Null Type provided, so add PSGalleryScripts repository
VERBOSE: Searching in repository PSGallery
VERBOSE: 2.5.2.0
VERBOSE: Null Type provided, so add PSGalleryScripts repository
VERBOSE: Searching in repository PSGallery
VERBOSE: Searching through package path: 'C:\Users\henry.buckle\Documents\WindowsPowerShell\Modules\Az.Accounts'
VERBOSE: Searching through package path: 'C:\Users\henry.buckle\Documents\WindowsPowerShell\Modules\Az.Accounts'
show more (open the raw output data in a text editor) ...
VERBOSE: Attempting to move 'C:\Users\henry.buckle\AppData\Local\Temp\76e3ca5f-c444-4a13-8225-6e7b6b1069f0\az.accounts\2.5.2' to 'C:\Users\henry.buckle\Documents\WindowsPowerShell\Modules\Az.Accounts\2.5.2'
VERBOSE: Successfully installed package 'Az.Accounts' to location 'C:\Users\henry.buckle\Documents\WindowsPowerShell\Modules'
VERBOSE: Attempting to delete 'C:\Users\henry.buckle\AppData\Local\Temp\76e3ca5f-c444-4a13-8225-6e7b6b1069f0'
VERBOSE: Successfully deleted 'C:\Users\henry.buckle\AppData\Local\Temp\76e3ca5f-c444-4a13-8225-6e7b6b1069f0'
Expected behavior
Installation path should be `Documents\PowerShell`Actual behavior
Installation path is `Documents\WindowsPowerShell`Error details
No response
Environment data
ModuleType Version PreRelease Name ExportedCommands
---------- ------- ---------- ---- ----------------
Binary 3.0.11 beta PowerShellGet {Find-PSResource, Get-Install…
Name Value
---- -----
PSVersion 7.1.3
PSEdition Core
GitCommitId 7.1.3
OS Microsoft Windows 10.0.19042
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0Visuals
No response
Reactions are currently unavailable
Activity
hbuckle commentedon Aug 12, 2021
Seems like for some reason the host version in .NET interactive is 0.0.1
anamnavi commentedon Aug 12, 2021
Henry Buckle (@hbuckle) thanks for reaching out!
Could you share your PS Modules path output with us by running:
$env:PSModulePathWe haven't yet done testing in the .NET interactive notebook and will test this scenario.
hbuckle commentedon Aug 13, 2021
This is PSModulePath from the .NET interactive kernel
alerickson commentedon Jul 14, 2022
I'm not sure when exactly this may have been resolved, but it looks like it is no longer an issue as of 3.0.14-beta14. I'm going to close this issue as resolved, but if you're still having this issue or see this issue pop up again in the future please let us know either here or in a new issue. Thanks!
hbuckle commentedon Oct 17, 2022
alerickson - I just tried this again and get the same issue with 3.0.17
hbuckle commentedon Oct 17, 2022
Save the following as a
.dibfile and open in VSCode with thems-dotnettools.dotnet-interactive-vscodeextensionWhen you run the cell you get the following
hbuckle commentedon Oct 17, 2022
I think the use of psCmdlet.Host.Version here is wrong - this is the version of the hosting application, not the PowerShell engine
https://github.com/PowerShell/PowerShellGet/blob/b005e0fff5fc02ca09e8502b947da9ea13c90b20/src/code/Utils.cs#L723
hbuckle commentedon Nov 3, 2022
alerickson, Anam Navied (@anamnavi) any update?
hbuckle commentedon Dec 29, 2022
If it helps this is how PowerShellEditorServices does it
https://github.com/PowerShell/PowerShellEditorServices/blob/main/src/PowerShellEditorServices/Utility/VersionUtils.cs
anamnavi commentedon Jan 9, 2023
Henry Buckle (@hbuckle) thanks for providing such thorough info, we'll investigate into this.
hbuckle commentedon Sep 18, 2023
alerickson alerickson - will it be fixed for GA? It looks like
psCmdlet.Host.Versionis still in useshoddyguard commentedon Mar 21, 2024
This is also an issue when using

RubyPwshPSHostwhich is what Puppet uses to call PowerShell.It would definitely be nice to have this fixed.
Borgquite commentedon Mar 27, 2026
Have just posted something in #1459 which may solve this.