Menu
Whenever I create a new MVC project, I am getting an error - failed to initialize Powershell host, for the entity framework and Jquery. The error: The following packages failed to install from 'C:\Program Files\Microsoft ASP.NET\ASP.NET MVC 4\Packages'
EntityFramework.5.0.0: Failed to initialize the Powershell host. If your powershell execution policy setting is set to AllSigned, open the package manager console to initialize the host first.
jQuery.1.7.1.1: Failed to initialize the Powershell host. If your powershell execution policy setting is set to AllSigned, open the package manager console to initialize the host first.
I can remove the Entity Framework reference, and add it manually, which is a good workaround, but it is annoying and a sign of some problem somewhere. Any ideas where to look?
This link documents a similar problem and workaround: http://social.msdn.microsoft.com/Forums/en/vssetup/thread/c934fed4-e44e-4a06-9e3b-eccb9c8aa8d6
238
Step2: Adding ADO.NET Entity Data Model in ASP.NET MVC Application. Right-Click on Models Folder, and then select Add => New Item from the context menu which will open the Add New Item window. From the “Add New Item” window, from the left pane expand Installed => Visual C# => Data option.
The @model directive allows access to the list of movies that the controller passed to the view by using a Model object that's strongly typed. For example, in the Index.cshtml view, the code loops through the movies with a foreach statement over the strongly typed Model object: CSHTML Copy.
Create the database context The main class that coordinates EF functionality for a given data model is the DbContext database context class. This class is created by deriving from the Microsoft. EntityFrameworkCore. DbContext class.
One of the replies on the MSDN thread worked for me. Run PowerShell as an Administrator and run the following command:
Set-ExecutionPolicy AllSigned See Using the Set-ExecutionPolicy Cmdlet for security implications.
81
This problem is fairly common - as there are multiple links to the MSDN forums and references to the workaround. I tried troubleshooting with the Package Manager in Visual Studio and noticed that it was frozen - with a reference to looking for C:\Program Files (x86)\7-Zip\7z.exe. No idea why, but I checked my system and sure enough, I have 7z installed in the standard Program Files (not x86). I made a copy in the x86 folder, reloaded Visual Studio and Visual Studio is now happy again. Not sure why there is a dependancy on 7zip in the Visual Studio Package Manager - but hopefully this will help another programmer ...
41
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
