none
Type name 'NuGet.VisualStudio.IVsPackageInstallerServices' is ambiguous

    Question

  • Hi All,

    After update Windows 10 Technical Preview to build 11099, my Package Manager in VS2015 dosn't work with EF.

    Add-Migration, Update-Database a have error

    Type name 'NuGet.VisualStudio.IVsPackageInstallerServices' is ambiguous, it could be 'NuGet.VisualStudio.IVsPackageInstallerServices, Microsoft.VisualStudio.ApplicationInsights, Version=4.0.0.0, Culture=neutr
    al, PublicKeyToken=b03f5f7f11d50a3a' or 'NuGet.VisualStudio.IVsPackageInstallerServices, Microsoft.VisualStudio.Web.Project, Version=2.3.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
    At C:\Users\ustal\Desktop\Aikikai\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1004 char:5
    +     $packageInstallerServices = $componentModel.GetService([NuGet.Vis ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
        + FullyQualifiedErrorId : AmbiguousTypeReference
     
    You cannot call a method on a null-valued expression.
    At C:\Users\ustal\Desktop\Aikikai\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1006 char:5
    +     $vsPackage = $packageInstallerServices.GetInstalledPackages() | ? ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\ustal\Desktop\Aikikai\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:713 char:28
    +     $toolsPath = Join-Path $installPath tools
    +                            ~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\ustal\Desktop\Aikikai\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:780 char:74
    + ...  [System.Reflection.Assembly]::LoadFrom((Join-Path $ToolsPath EntityF ...
    +                                                        ~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    You cannot call a method on a null-valued expression.
    At C:\Users\ustal\Desktop\Aikikai\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:781 char:5
    +     $dispatcher = $utilityAssembly.CreateInstance(
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\ustal\Desktop\Aikikai\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:810 char:20
    +         (Join-Path $runner.ToolsPath EntityFramework.PowerShell.dll),
    +                    ~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     

    This error if i try renistall EF from NuGet

    • Edited by Alexey.U Saturday, January 16, 2016 7:39 PM
    Saturday, January 16, 2016 7:31 PM

All replies

  • Also had the same problem, under the same circumstances - after updating to Windows 10 Enterprise Insider Preview 11099 - with a slightly different output:

    Type name 'NuGet.VisualStudio.IVsPackageInstallerServices' is ambiguous, it could be 'NuGet.VisualStudio.IVsPackageInstallerServices, 
    Microsoft.VisualStudio.Authentication.ConnectedServices, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or 'NuGet.VisualStudio.IVsPackageInstallerServices, 
    Microsoft.Pex.VisualStudio, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
    At C:\Users\Mateus Rodrigues\OneDrive\Developer\Visual Studio\SiCond\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1004 char:5
    +     $packageInstallerServices = $componentModel.GetService([NuGet.Vis ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
        + FullyQualifiedErrorId : AmbiguousTypeReference
     
    You cannot call a method on a null-valued expression.
    At C:\Users\Mateus Rodrigues\OneDrive\Developer\Visual Studio\SiCond\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1006 char:5
    +     $vsPackage = $packageInstallerServices.GetInstalledPackages() | ? ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\Mateus Rodrigues\OneDrive\Developer\Visual Studio\SiCond\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:713 char:28
    +     $toolsPath = Join-Path $installPath tools
    +                            ~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\Mateus Rodrigues\OneDrive\Developer\Visual Studio\SiCond\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:780 char:74
    + ...  [System.Reflection.Assembly]::LoadFrom((Join-Path $ToolsPath EntityF ...
    +                                                        ~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    You cannot call a method on a null-valued expression.
    At C:\Users\Mateus Rodrigues\OneDrive\Developer\Visual Studio\SiCond\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:781 char:5
    +     $dispatcher = $utilityAssembly.CreateInstance(
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\Mateus Rodrigues\OneDrive\Developer\Visual Studio\SiCond\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:810 char:20
    +         (Join-Path $runner.ToolsPath EntityFramework.PowerShell.dll),
    +                    ~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     

    I still haven't been able to find a workaround or solution to this.

    Saturday, January 16, 2016 7:53 PM
  • After update Windows 10 Technical Preview to build 11099, my Package Manager in VS2015 dosn't work with EF.

    Why are you using some Preview?

    Sunday, January 17, 2016 12:09 AM
  • I also had the exact same issue. I reverted back to 11082 and everything is working fine now.
    Sunday, January 17, 2016 12:50 AM
  • Similar issue - I get the following when trying to do Add-Migration

    Type name 'Microsoft.VisualStudio.Shell.Package' is ambiguous, it could be 'Microsoft.VisualStudio.Shell.Package, Microsoft.VisualStudio.Shell.14.0,
    Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or 'Microsoft.VisualStudio.Shell.Package, Microsoft.VisualStudio.Shell.11.0, Version=14.0.0.0,
    Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
    At C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\R1FURSGJ.FQI\Modules\NuGet\profile.ps1:126 char:5
    +     $service = [Microsoft.VisualStudio.Shell.Package]::GetGlobalServi ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
        + FullyQualifiedErrorId : AmbiguousTypeReference
     
    Type name 'NuGet.VisualStudio.IVsPackageInstallerServices' is ambiguous, it could be 'NuGet.VisualStudio.IVsPackageInstallerServices, WebCompilerVsix,
    Version=1.9.287.0, Culture=en-US, PublicKeyToken=null' or 'NuGet.VisualStudio.IVsPackageInstallerServices, Microsoft.VisualStudio.ApplicationInsights,
    Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
    At C:\xxxxxxxxxxxxx\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1004 char:5
    +     $packageInstallerServices = $componentModel.GetService([NuGet.Vis ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
        + FullyQualifiedErrorId : AmbiguousTypeReference
     
    You cannot call a method on a null-valued expression.
    At C:\xxxxxxxxxxxxx\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1006 char:5
    +     $vsPackage = $packageInstallerServices.GetInstalledPackages() | ? ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\xxxxxxxxxxxxx\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:713 char:28
    +     $toolsPath = Join-Path $installPath tools
    +                            ~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\xxxxxxxxxxxxx\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:780 char:74
    + ...  [System.Reflection.Assembly]::LoadFrom((Join-Path $ToolsPath EntityF ...
    +                                                        ~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    You cannot call a method on a null-valued expression.
    At C:\xxxxxxxxxxxxx\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:781 char:5
    +     $dispatcher = $utilityAssembly.CreateInstance(
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\xxxxxxxxxxxxx\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:810 char:20
    +         (Join-Path $runner.ToolsPath EntityFramework.PowerShell.dll),
    +                    ~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand

    I am also on Windows 10 Pro Insider Preview 11099.rs1_release.160109-1156

    Monday, January 18, 2016 5:03 PM
  • Same here having the same issues with Type name 'Microsoft.VisualStudio.Shell.Package' is ambiguous

    Regards..

    Peter

    Tuesday, January 19, 2016 12:15 AM
  • Same issue here. I've had to resort to using the migrate.exe tool that comes with EF to run migrations for now. That works fine except I usually generate change scripts with package manager, but migrate.exe doesn't seem to support that.
    Tuesday, January 19, 2016 5:12 PM
  • Getting error Visual Studio after upgrading to Windows 10 11099

    and trying to update database in EF 6.1

    After update Windows 10 Technical Preview to build 11099, my Package Manager in VS2015 dosn't work with EF.

    Add-Migration, Update-Database a have error

    Type name 'NuGet.VisualStudio.IVsPackageInstallerServices' is ambiguous, it could be 'NuGet.VisualStudio.IVsPackageInstallerServices, Microsoft.VisualStudio.ApplicationInsights, Version=4.0.0.0, Culture=neutr
    al, PublicKeyToken=b03f5f7f11d50a3a' or 'NuGet.VisualStudio.IVsPackageInstallerServices, Microsoft.VisualStudio.Web.Project, Version=2.3.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
    At C:\Users\ustal\Desktop\Aikikai\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1004 char:5
    +     $packageInstallerServices = $componentModel.GetService([NuGet.Vis

    ........


    Wednesday, January 20, 2016 5:36 PM
  • Just updated to build 11102 and the issue is still present.
    Friday, January 22, 2016 1:42 AM
  • I had the same error (also on Windows 10.0.11099), but it seems to be caused (at least for me) by having different .NET versions in the same solution (I had one 4.5.2 project and a bunch of 4.5 projects) once I set the same version to all projects and restarted Visual Studio the Add-Migration and Update-Database started working again.
    Friday, January 22, 2016 7:36 AM
  • Problem still present in latest build, 11102.rs1_release.160113-1800

    Scott

    Friday, January 22, 2016 4:20 PM
  • I have only one project. Also, I tried creating a new project/sln and still have this issue.

    Mine shows multiple Ambiguous references in

    C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\PPBMHMT1.4I0\Modules\NuGet\profile.ps1:126 char:5

    $service = [Microsoft.VisualStudio.Shell.Package]::GetGlobalService($ServiceType)


    Scott


    • Edited by ScottRegitz Friday, January 22, 2016 5:27 PM
    Friday, January 22, 2016 5:18 PM
  • Windows-Feedback:?contextid=532&feedbackid=06e38a2b-af91-4c20-8196-98bb030f2483&form=1&src=2

    same issue(s) for me. posted in feedback tool.


    Thanks



    • Edited by Marmarpo Saturday, January 23, 2016 3:42 PM
    Saturday, January 23, 2016 3:38 PM
  • Sorry, but I updated to build 11102 and the issue is still present.

    RT

    Sunday, January 24, 2016 9:54 AM
  • Hi Alexey,

    According to your description, I suggest that you could post this scenario to: https://github.com/aspnet/EntityFramework/issues

    Microsoft engineers will evaluate them seriously. Thanks for your understanding.

    Best regards,

    Cole Wu

    Monday, January 25, 2016 1:23 AM
    Moderator
  • Hi Cole,

    It seems that the issue is related to Visual Studio Shell as the error message points that there are two assemblies registered as pointed out below

    Type name 'Microsoft.VisualStudio.Shell.Package' is ambiguous, it could be 'Microsoft.VisualStudio.Shell.Package, Microsoft.VisualStudio.Shell.14.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or 'Microsoft.VisualStudio.Shell.Package, 
    Microsoft.VisualStudio.Shell.10.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
    At C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\3TD5DHUM.UVP\Modules\NuGet\profile.ps1:126 char:5
    +     $service = [Microsoft.VisualStudio.Shell.Package]::GetGlobalServi ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
        + FullyQualifiedErrorId : AmbiguousTypeReference

    Somehow the Shell is not being able to distinguish which one is the right to call - all of this came with the new Update 1 and was disrupted with the new Insider builds.


    Monday, January 25, 2016 12:01 PM
  • FYI this issue is also being tracked on the EF6 Codeplex page.

    http://entityframework.codeplex.com/workitem/2872

    Tuesday, January 26, 2016 7:30 PM
  • Hi Alexey,

    According to your description, I suggest that you could post this scenario to: https://github.com/aspnet/EntityFramework/issues

    Microsoft engineers will evaluate them seriously. Thanks for your understanding.

    Best regards,

    Cole Wu

    posted https://github.com/aspnet/EntityFramework/issues/4443

    Thanks

    Saturday, January 30, 2016 5:05 PM
  • Still present in 14251 as well
    Saturday, January 30, 2016 5:56 PM
  • in 14257 too

    Friday, February 05, 2016 7:50 PM
  • As HaydenM pointed out, the place to follow up this issue is on codeplex and they are looking to identify the root cause of what it is not working as I got a message there from @divega. Not only the EF team, but also the Windows and Visual Studio teams are looking why it is not working as expected.
    Friday, February 05, 2016 7:55 PM
  • I have figured out a workaround for this issue using type aliases.  I wrote it in more detail in my blog here.

    - Stefan Z Camilleri - http://edd.stefancamilleri.com

    Sunday, February 14, 2016 1:03 AM
  • @Stefan-Z-Camilleri

    This is great - my only concern is that the MS teams de-prioritise this now there is a workaround available. Here's hoping they can either build on what you've done or come up with a 'real' solution to the underlying problem/change and that they do it soon.
    In the mean time - many thanks as I have been having to try and do EF work on a Hyper-V instance which has not, so far, been very successful.
    Cheers, Cynthia

    • Edited by CZEMacLeod Wednesday, February 17, 2016 4:23 PM
    Wednesday, February 17, 2016 4:22 PM
  • Build 14267 have the same problem. Haven’t tried the workaround yet, but will definitely try now.
    Friday, February 19, 2016 2:44 PM
  • Yup :( I get you.

    - Stefan Z Camilleri - http://edd.stefancamilleri.com

    Wednesday, February 24, 2016 2:38 AM
  • Hi,

       Still getting it in the new release, but different error with the work around applied..

    Regards..

    Peter

    Wednesday, February 24, 2016 12:35 PM
  • I guess that means that in your case, you're past one error and onto the next :(  This only fixes the aforementioned error.

    You seem to have a new one... maybe you can post it so we can see what it is?


    - Stefan Z Camilleri - http://edd.stefancamilleri.com

    Thursday, February 25, 2016 3:11 AM
  • Hi,

    After applying the 2 changes, it seems to move forward - but then I see this:

    Get-VsComponentModel : The term 'Get-VsComponentModel' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct 
    and try again.
    At <>/EntityFramework.6.1.3\tools\EntityFramework.psm1:1003 char:23
    +     $componentModel = Get-VsComponentModel
    +                       ~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Get-VsComponentModel:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
     
    You cannot call a method on a null-valued expression.
    At <>/EntityFramework.6.1.3\tools\EntityFramework.psm1:1008 char:5
    +     $packageInstallerServices = $componentModel.GetService([NuGetInst ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At <>/EntityFramework.6.1.3\tools\EntityFramework.psm1:1011 char:5
    +     $vsPackage = $packageInstallerServices.GetInstalledPackages() | ? ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At <>\EntityFramework.6.1.3\tools\EntityFramework.psm1:713 char:28
    +     $toolsPath = Join-Path $installPath tools
    +                            ~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At <>\EntityFramework.6.1.3\tools\EntityFramework.psm1:780 char:74
    + ...  [System.Reflection.Assembly]::LoadFrom((Join-Path $ToolsPath EntityF ...
    +                                                        ~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    You cannot call a method on a null-valued expression.
    At <>\EntityFramework.6.1.3\tools\EntityFramework.psm1:781 char:5
    +     $dispatcher = $utilityAssembly.CreateInstance(
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At <>\EntityFramework.6.1.3\tools\EntityFramework.psm1:810 char:20
    +         (Join-Path $runner.ToolsPath EntityFramework.PowerShell.dll),
    +                    ~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand


    • Edited by RT1969 Thursday, February 25, 2016 9:34 PM
    Thursday, February 25, 2016 9:32 PM
  • Sorry about the above. I debugged this myself and realized that when I copied/pasted Stefan-Z's commands from here, for some reason the double quotes were not copied and pasted correctly. Once I changed those, things are looking much better - so far.

    I will leave these posts here since it might help others - make sure the buffer from here is copied and pasted correctly into those 2 files.

    Thanks Stefan-Z.

    Thursday, February 25, 2016 9:53 PM
  • Hi,

        Had a similar issue as RT1969 with the double quotes, once corrected I then received the error with the  "NuGet.VisualStudio.IVsPackageInstallerServices".

    I applied the fix as described from "http://edd.stefancamilleri.com/2016/02/14/update-database-fails-in-package-manager-console-on-windows-10-insider-preview-with-ambiguous-type-error/" and from that I now have the following error..

    PM> update-database
    Cannot convert argument "type", with value: "NuGet.VisualStudio.IVsPackageInstallerServices, Xamarin.VisualStudio.IOS.Migration.Shell, Version=104.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756", for "Add" to type "System.Type": "Cannot
    convert the "NuGet.VisualStudio.IVsPackageInstallerServices, Xamarin.VisualStudio.IOS.Migration.Shell, Version=104.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756" value of type "System.String" to type "System.Type"."
    At C:\Users\Peter\documents\visual studio 2015\Projects\EFTest\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1006 char:2
    +     $accel::add("NuGetInstallerServices","NuGet.VisualStudio.IVsPacka ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [], MethodException
        + FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument
     
    Unable to find type [NuGetInstallerServices].
    At C:\Users\Peter\documents\visual studio 2015\Projects\EFTest\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1007 char:57
    + ... tallerServices = $componentModel.GetService([NuGetInstallerServices])
    +                                                 ~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (NuGetInstallerServices:TypeName) [], RuntimeException
        + FullyQualifiedErrorId : TypeNotFound
     
    You cannot call a method on a null-valued expression.
    At C:\Users\Peter\documents\visual studio 2015\Projects\EFTest\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:1009 char:5
    +     $vsPackage = $packageInstallerServices.GetInstalledPackages() | ? ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\Peter\documents\visual studio 2015\Projects\EFTest\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:713 char:28
    +     $toolsPath = Join-Path $installPath tools
    +                            ~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\Peter\documents\visual studio 2015\Projects\EFTest\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:780 char:74
    + ...  [System.Reflection.Assembly]::LoadFrom((Join-Path $ToolsPath EntityF ...
    +                                                        ~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    You cannot call a method on a null-valued expression.
    At C:\Users\Peter\documents\visual studio 2015\Projects\EFTest\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:781 char:5
    +     $dispatcher = $utilityAssembly.CreateInstance(
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Join-Path : Cannot bind argument to parameter 'Path' because it is null.
    At C:\Users\Peter\documents\visual studio 2015\Projects\EFTest\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:810 char:20
    +         (Join-Path $runner.ToolsPath EntityFramework.PowerShell.dll),
    +                    ~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
     
    PM>

    Regards

    Peter A.

    Saturday, February 27, 2016 9:47 AM