You can press the Tab key after entering a few characters to trigger the autocomplete functionality. To get help on any command, you can type the command Get-help. Now, you can go ahead and type a command to install a new package in your project: Let's see some quick examples of the usage. For example: EntityFramework adds a host of commands to manage code first migrations.

Many packages add commands to PMC for additional functionality.

PMC is not just an alternative to NuGet.

The PMC scripts can also be part of the continuous integration system.

This provides a kind of repair functionality.

PMC can also be useful to reinstall a package using the -reinstall flag.

PMC is useful if you wish to manage the dependencies manually without using NuGet, for example to install a package without dependencies use the flag -IgnoreDependencies.

NuGet will always install the latest version of a package however, using PMC you can specify the version number of the package to install.

The PMC scripts can be part of the Visual Studio solution itself so that any new team member can simply run those scripts when setting up the solution.

Using PMC, you can automate the addition of packages into your solution instead of each team member going to the NuGet UI to add packages.So, why should you bother to use PMC given that you have a nice UI for the NuGet system integrated in Visual Studio? The following are the benefits of using PMC over the NuGet UI: The following is a screen shot for the console:īenefits of using Package Manager Console (PMC) You can access the Package Manager Console from within Visual Studio by going to Tools -> Library Package Manager -> Package Manager Console. The Package Manager Console is a PowerShell console within Visual Studio used to interact with NuGet and automate Visual Studio.

Visual studio 2014 for mac