8000 Unexpected module loading through NuGet · Issue #3325 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]
Skip to content

Unexpected module loading through NuGet #3325

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.

Sign up for GitHub

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

Jump to bottom
Closed
chunqingchen opened this issue Mar 13, 2017 · 4 comments
Closed

Unexpected module loading through NuGet #3325

chunqingchen opened this issue Mar 13, 2017 · 4 comments
Assignees
@chunqingchen
Labels
Issue-Discussion the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif Resolution-Fixed The issue is fixed. WG-Engine core PowerShell engine, interpreter, and runtime
Milestone
6.0.0-GA

Comments

@chunqingchen
Copy link
Contributor

Steps to reproduce

Get VS 2017 RTW.
Install an “experimental” VSIX of NuGet like the one here by double clicking on it:
\nuget\nuget\Share\Drops\CI\NuGet.Client\dev\2381\artifacts\VS15\NuGet.Tools.vsix
Open PackageManagerConsole…

Expected behavior

correct version of 'NuGet.PackageManagement.PowerShellCmdlets.dll' is loaded

Actual behavior

the wrong NuGet.PackageManagement.PowershellCmdlets.dll is pulled in

Environment data

PSVersion 5.1.14393.693
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.693
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
@chunqingchen chunqingchen self-assigned this Mar 13, 2017
@nkolev92 nkolev92 mentioned this issue Mar 13, 2017
Closed
@SteveL-MSFT
Copy link
Member

Seems like this is an issue with VS2017 which hosts PowerShell and has their own PackageManagement module?

@alpaix
Copy link
alpaix commented Mar 13, 2017

NuGet Package Manager Console (PMC) hosts PowerShell for running NuGet cmdlets and executing install/uninstall/init package scripts. It imports <extension root>\Modules\NuGet\NuGet.psd1 module which in its turn depends on a nested module NuGet.PackageManagement.PowerShellCmdlets.dll.

The last one is loaded from wrong location when working with "experimental" VS instance.

@iSazonov iSazonov added the Issue-Discussion the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif label Mar 15, 2017
@nkolev92
Copy link

Any updates here?
ETA?

@chunqingchen chunqingchen added this to the 6.0.0-HighPriority milestone Jun 21, 2017
@chunqingchen chunqingchen mentioned this issue Jul 7, 2017
Merged
@SteveL-MSFT SteveL-MSFT added the WG-Engine core PowerShell engine, interpreter, and runtime label Jul 7, 2017
@iSazonov iSazonov added the Resolution-Fixed The issue is fixed. label Oct 4, 2017
@SteveL-MSFT SteveL-MSFT removed the Resolution-Fixed The issue is fixed. label Oct 12, 2017
@SteveL-MSFT SteveL-MSFT reopened this Oct 12, 2017
@SteveL-MSFT SteveL-MSFT mentioned this issue Oct 12, 2017
Closed
@chunqingchen chunqingchen mentioned this issue Oct 19, 2017
Merged
@daxian-dbw
Copy link
Member

Close via #5161

@iSazonov iSazonov added the Resolution-Fixed The issue is fixed. label Nov 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chunqingchen chunqingchen

Labels
Issue-Discussion the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif Resolution-Fixed The issue is fixed. WG-Engine core PowerShell engine, interpreter, and runtime
Projects
None yet
Milestone
6.0.0-GA
Development

No branches or pull requests
6 participants
@daxian-dbw @nkolev92 @alpaix @SteveL-MSFT @chunqingchen @iSazonov
0