Skip to content
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

Nuget package manager update 3.1.1.0 broken #1125

Closed
shmao opened this issue Aug 6, 2015 · 4 comments
Closed

Nuget package manager update 3.1.1.0 broken #1125

shmao opened this issue Aug 6, 2015 · 4 comments
Assignees
Labels
Priority:2 Issues for the current backlog. Product:VS.Client Type:Bug
Milestone

Comments

@shmao
Copy link

shmao commented Aug 6, 2015

Quoting from this Stackoverflow post:

I updated Nuget package manager to version 3.1.1.0. After the update opening any project gives me the error message: copy-item: cannot find path 'c:\users{username}\documents\visual studio 2015\projects{project name}\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\tools\lib\net45' because it does not exist ..... in file init.ps1

I found $installpath variable given to init.ps1 differs from old nuget to actual in additionally appended \tools subdirectory name, which is obviously wrong and gives the error.

I double-checked this behaviour also in a fresh installed vm with the same result, VS installed -> ok, update to nuget 3.1.1 -> broken.

Environment: Windows 10 German, Visual Studio 2015 Community Edition English

@yishaigalatzer
Copy link

This package needs to move off init.ps1, regardlesss this looks like a valid concern.

@yishaigalatzer
Copy link

Verified this does not repro in Visual Studio 2013.

@zhili1208 please add a functional test to cover this scenario going forward

@zhili1208
Copy link
Contributor

Verified this does not repro on Visual studio 2013, this bug only happens during Powershell console initialization, so function test can't hit this bug, only UI can hit this. we might can add a test to manual verification

@deepakaravindr
Copy link

Did the following for verification

  1. Created a project and installed Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0 on it.
  2. Closed PMC if it was open and closed VS
  3. Re-opened VS and opened the solution created in Step-1
  4. Deleted files Microsoft.CodeDom.Providers.DotNetCompilerPlatform.dll and the xml from \bin if present. Note that init.ps1 from the package in question should add these files to \bin folder after execution
  5. Opened Package Manager Console and let it complete initialization
  6. Verified that files Microsoft.CodeDom.Providers.DotNetCompilerPlatform.dll and the xml are created back in \bin folder indicating that init.ps1 ran successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:2 Issues for the current backlog. Product:VS.Client Type:Bug
Projects
None yet
Development

No branches or pull requests

4 participants