My passport for mac staples. I'm super excited about the release of PowerShell for Mac and Linux--congrats! However, I ran into some trouble trying to use Nuget commands. Lots of documentation on NuGet packages seems to assume that you're using Windows and the VS Package Manager Console, so I was looking forward to being able to follow these sorts of examples in a straightforward manner when developing for ASP.Net on OSX (example: adding a package to my project through the command line, like Install-Package ) Here's what I did, hoping it would work. • Installed PowerShell using.pkg installer on OS X • Opened a terminal and entered powershell • Typed Install-Package -ListAvailable, which was as something you could do with the Package Manager Console. • Got this error: Get-Package: A parameter cannot be found that matches parameter name 'ListAvailable'. So it looks like the Get-Packagecommand is something that PowerShell recognizes, but it doesn't behave the same way as it does in the VS Package Manager Console. Lib Support NuGet 4.8 in Visual Studio for Mac 7.7.2, 12 days ago. Installing a NuGet package from the unified search; Listing Portable Class Libraries. Xamarin package and install it to their projects following these steps: Select the. Select which projects will have the package installed. Visual Studio for Mac. Commented on this issue at 's: PowerShell nuget package manager (the one from Visual Studio) has cmdlet's name collisions with PowerShellGet (PS package manager), which you run in PowerShell on OS X. They essentially provide the same functionality for different scopes (project vs the whole system), but available parameters are different. It's indeed confusing, we are sorry. I'm kind of new to PowerShell, so I don't know if making this work would require changes with PowerShell itself, or if there is something I can do to my configuration let it know that I want to behave similar to the VS Package Manager Console. Link to doesn't go anywhere. There is no link to the Windows 10 guide mentioned. Searching on docs.nuget.org for powershell profile gives a doc at which describes that you might use a Powershell profile for nuget, but just links to an explanation of powershell profiles and doesn't give any hints to a powershelll newbie. Right now I am trying to get my Mac set up to manage Azure using Powershell and it is a dependancy nightmare. I'm unable to find a document that will take me all the way to this goal. So far, I've installed powershell, which works but I can't install packages. Then I install nuget, which requires mono. ![]() I've installed both those. But powershell can't use nuget to get anything without further configuration or something I'm missing. Is there any guidance to get someone up and running quickly without them having first to learn everything? ![]() The thing is, I don't want to write code. I'm a sysadmin who needs to admin Azure VMs using powershell. I don't need an ide etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |