none
Package Manager console failed to load RRS feed

  • Question

  • Last night I installed update 3 for Visual Studio 2012 professional (version 11.0.60610.01).  This morning when I started the package manager console I received the following errors.  I did a repair of VS but other than taking a long time it did not fix anything.  I also installed all the extension updates, no help either.  The file mention below is where it should be and I can open it.  Tried running in administrator mode, again no help.  All three versions of power shell seem to run just fine (64, 86, ISE).  I am running Windows 8 on a 64 bit machine, all updates are installed.

    Any suggestions on how to fix this one?

    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(2977) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(2984) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(2991) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(2998) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The following error occurred while loading the extended type data file: Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(3005) : Error in type "System.Security.AccessControl.ObjectSecurity": Exception: The getter method should be public, non void, static, and have one parameter of type PSObject.
    The term 'Get-ExecutionPolicy' 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.



    John J. Hughes II

    Ran Get-ExecutionPolicy from PowerShell (x86) it returns Restricted

    Also looking around... I have on add-in installed or running

    Also tried uninstalling nugget and reinstalling


    I noticed on the NuGet website it calls for PowerShell 2.0. It seems I have PowerShell 3.0, could that be a problem? Can I install PowerShell 2.0/3.0 side by side, is there an update to NuGet?
    Thursday, June 27, 2013 1:29 PM

Answers

  • Found the following link in stack overflow, added the suggested items to the VS exe config file and it works now without error.

    http://stackoverflow.com/questions/12638289/embedding-powershell-v2-0-in-net-app-on-windows-8-rtm

    Added the following to the devenv.exe.config file in the runtime section

            <dependentAssembly>
                <assemblyIdentity name="System.Management.Automation" publicKeyToken="31bf3856ad364e35" />
                <publisherPolicy apply="no" />
              </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.Commands.Utility" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.ConsoleHost" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.Commands.Management" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.Security" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.Commands.Diagnostics" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
    


    John J. Hughes II

    Tuesday, July 2, 2013 2:30 PM

All replies

  • Hi John,

    Do you mean that it worked well before you install the update 3?

    Actually this forum is to discuss: Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.

    I might not have the correct detailed answer you need, but I might lead you into the right direction to solve your problem.

    Can I install PowerShell 2.0/3.0 side by side?

    Since this issue is related to PowerShell, you could post this issue:

    http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverpowershell

    Package Manager console  

    If this issue is related the extension tool “NuGet Package Manager”? Maybe you could get the correct place for this issue here.

    If I have misunderstood anything, please make free feel to let me know.

    Best Regards,


    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, July 1, 2013 6:36 AM
    Moderator
  • Thanks Jack,

    Yes the issue started when I installed update 3.

    No I don't know if it is a power shell problem or a NuGet problem.

    Is there a NuGet forum, I could not find one.  Don't think this relates to power shell but I could ask about the powershell 2/3.

    Is there a VS update forum?


    John J. Hughes II

    Monday, July 1, 2013 11:19 AM
  • Hi John,

    Sorry for that I didn’t find the specific forum for NuGet issue, but you could post an issue in the forum ("Where is the forum for..?"). The owner of the forum will direct you to a right forum.

    Is there a VS update forum?

    My suggestion is that you could remove this update from your machine, and then check it again. If it works well, so we could make sure that it is the VS update issue, of course, maybe you could re-install it.

    If we could make sure that it is the VS update issue, you can submit this feedback to Microsoft Connect feedback portal: http://connect.microsoft.com, Microsoft engineers will evaluate them seriously. Thanks for your understanding.

    Best Regards,


    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, July 2, 2013 4:43 AM
    Moderator
  • Found the following link in stack overflow, added the suggested items to the VS exe config file and it works now without error.

    http://stackoverflow.com/questions/12638289/embedding-powershell-v2-0-in-net-app-on-windows-8-rtm

    Added the following to the devenv.exe.config file in the runtime section

            <dependentAssembly>
                <assemblyIdentity name="System.Management.Automation" publicKeyToken="31bf3856ad364e35" />
                <publisherPolicy apply="no" />
              </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.Commands.Utility" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.ConsoleHost" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.Commands.Management" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.Security" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
            <dependentAssembly>
              <assemblyIdentity name="Microsoft.PowerShell.Commands.Diagnostics" publicKeyToken="31bf3856ad364e35" />
              <publisherPolicy apply="no" />
            </dependentAssembly>
    


    John J. Hughes II

    Tuesday, July 2, 2013 2:30 PM
  • Hi John,

    Glad to see this issue has been resolved and thank you for sharing your solutions here. It will be very beneficial for other community members who have similar questions.

    Have a nice day,


    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, July 3, 2013 5:04 AM
    Moderator
  • I have the exact same problem in that NuGet Package Manager will not launch/start after updating to Visual Studio Update 3.  I tried what you suggested above, but it did not work for me.  I wanted to make sure I am adding the correct information to the correct file as you describe above.  I am adding the text you show above to:

    C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe.config

    and I am adding this information under the runtime section and then under

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">,

    I also tried to load this directly under the run section without any success. 

    So my questions are:

    Is this the correct file and location within the file?

    Do I have to uninstall/reinstall the NuGet Package Manager once I have done this?

    After either change I do not even see the NuGet Package Manager when I load my solution and so I cannot even attempt to launch NuGet. 

    Thanks in advance

    Tuesday, July 9, 2013 7:12 PM
  • Yes the file location is correct yes the location in the file seem correct, I put mine at the end of that group just after the last </dependatnAssembly> and before </dependentAssembly>.

    I always has the package manager in the "tools->library package manager" menu so if you don't have it I would suggest installing it again.  I would also suggest you look at "tools->extensions and updates" to make sure you have all the updates installed.  If you open the extensions and updates the nugget package manager should be listed with the uninstall option.

    Note the system that was on went belly up and I am waiting for replacement parts so can't look at the file now.  On my laptop I install VS and update 3 with no problems, maybe it has to do with going from 2 to 3 or something else, not sure.  My desk and laptop are running basically the same configuration other than the hardware so not sure why there is a problem, again I think it depends on what was installed prior to the update.


    John J. Hughes II
    www.functioninternational.com

    Tuesday, July 9, 2013 8:13 PM
  • Made these changes/additions within the devenv.exe.config and disabling the "PowerShell Tools for Visual Studio 2013" helped me out.

    Thank you.


    • Edited by NitroAMD Monday, April 6, 2015 11:48 AM
    Monday, April 6, 2015 11:47 AM
  • I have this issue with vs 2008, 2013 and now 2017.  I tried these fixes including update and re-install.  Still broken.
    Tuesday, January 16, 2018 6:54 PM
  • Hi PCTony,

    Since this thread was closed for a long time, if possible, please open a new case in this forum, we will follow up it in time.

    Best Regards,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, January 17, 2018 1:29 AM
    Moderator