path issue in init.ps1 (line 10) in Microsoft.CodeDom.Providers.DotNetCompilerPlatform 1.0.0.0 nuget package on VS2015 / .Net 4.6

[todthomson]

Just wanted to loop you in on (what seems like) a bug / path issue in init.ps1 (line 10) in Microsoft.CodeDom.Providers.DotNetCompilerPlatform 1.0.0.0 nuget package on VS2015 / .Net 4.6 / NuGet Package Manager 3.1.1.0.

On opening the package manger console window I get the following error:

Copy-Item : Cannot find path 'C:\Development\GitHub\pd-tech-demo\backend\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\tools\lib\net45' because it does not exist.
At C:\Development\GitHub\pd-tech-demo\backend\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\tools\init.ps1:23 char:1
+ Copy-Item $libDirectory\* $binDirectory | Out-Null
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (C:\Development\...tools\lib\net45:String) [Copy-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

I changed line 10 of init.ps1 from:

$libDirectory = Join-Path $installPath 'lib\net45'

to:

$libDirectory = Join-Path $installPath '..\lib\net45'

which fixes the problem (only until you restore the package again and you get the broken version).

Original on Stack Overflow: http://stackoverflow.com/questions/31770339/nuget-package-manager-update-3-1-1-0-broken/31826795

[Pilchie]

This package is not owned by the Roslyn team, but the Web tools team. If you want to be able to track it, you should file a bug on http://connect.microsoft.com/. If you don't want to track, I'll be happy to file it internally for you.

[todthomson]

If you don't want to track, I'll be happy to file it internally for you.

That would be great 👍 thanks.

[tkirill]

+1 encounter this issue today too.

[yishaigalatzer]

Tracking a potential issue in NuGet here - NuGet/Home#1125, and working directly with the package owner on dropping init.ps1

[DrLeh]

+1 I also encountered this, cannot install this package.

[yishaigalatzer]

The issue is now fixed in nuget. This is not a Roslyn issue. Will be available in 3.2

[MaximeKoitsalu]

+1

[yishaigalatzer]

@maxkoi nuget 3.2 is available, please update your nuget extension

[todthomson]

The issue is now fixed in nuget. This is not a Roslyn issue. Will be available in 3.2

If someone can confirm this is fixed then please close this issues as "fixed"

[9gix]

Upgrading to nuget 3.2 solve my problem. 👍

[jmarolf]

Closing as this is not Roslyn specific