- Microsoft Packages For Smithsonian For Mac Pro
- Microsoft Packages For Smithsonian For Mac 2016
- Microsoft Packages For Smithsonian For Mac Download
- Microsoft Packages For Smithsonian For Mac 2017
Download this app from Microsoft Store for Windows 10, Windows 8.1. See screenshots, read the latest customer reviews, and compare ratings for Smithsonian at Home. Download this game from Microsoft Store for Windows 10. See screenshots, read the latest customer reviews, and compare ratings for Hidden Expedition: Smithsonian Castle. For the macOS platform, you can install the Azure CLI with homebrew package manager. Homebrew makes it easy to keep your installation of the CLI update to date. The CLI package has been tested on macOS versions 10.9 and later. The current version of the Azure CLI is 2.0.75.
-->Looking to install a package? See Ways to install NuGet packages.
To work with NuGet, as a package consumer or creator, you can use command-line interface (CLI) tools as well as NuGet features in Visual Studio. This article briefly outlines the capabilities of the different tools, how to install them, and their comparative feature availability. To get started using NuGet to consume packages, see Install and use a package (dotnet CLI) and Install and use a package (Visual Studio). To get started creating NuGet packages, see Create and publish a NET Standard package (dotnet CLI) and Create and publish a NET Standard package (Visual Studio).
Tool | Description | Download |
---|---|---|
dotnet.exe | CLI tool for .NET Core and .NET Standard libraries, and for any SDK-style project such as one that targets .NET Framework. Included with the .NET Core SDK and provides core NuGet features on all platforms. (Starting in Visual Studio 2017, the dotnet CLI is automatically installed with any .NET Core related workloads.) | .NET Core SDK |
nuget.exe | CLI tool for .NET Framework libraries and for any non-SDK-style project such as one that targets .NET Standard libraries. Provides all NuGet capabilities on Windows, provides most features on Mac and Linux when running under Mono. | nuget.exe |
Visual Studio | On Windows, the NuGet Package Manager is included with Visual Studio 2012 and later. Visual Studio provides the Package Manager UI and the Package Manager Console, through which you can run most NuGet operations. | Visual Studio |
Visual Studio for Mac | On Mac, certain NuGet capabilities are built-in directly. Package Manager Console is not presently available. For other capabilities, use the dotnet.exe or nuget.exe CLI tools. | Visual Studio for Mac |
Visual Studio Code | On Windows, Mac, or Linux, NuGet capabilities are available through marketplace extensions, or use the dotnet.exe or nuget.exe CLI tools. | Visual Studio Code |
The MSBuild CLI also provides the ability to restore and create packages, which is primarily useful on build servers. MSBuild is not a general-purpose tool for working with NuGet.
Package Manager Console commands work only within Visual Studio on Windows and do not work within other PowerShell environments.
Microsoft Packages For Smithsonian For Mac Pro
Visual Studio
Install on Visual Studio 2017 and newer
Starting in Visual Studio 2017, the installer includes the NuGet Package Manager with any workload that employs .NET. To install separately, or to verify that the Package Manager is installed, run the Visual Studio installer and check the option under Individual Components > Code tools > NuGet package manager.
Install on Visual Studio 2015 and older
NuGet Extensions for Visual Studio 2013 and 2015 can be downloaded from https://dist.nuget.org/index.html.
For Visual Studio 2010 and earlier, install the 'NuGet Package Manager for Visual Studio' extension. Note, if you can't see the extension in the first page of search results, try changing the Sort By dropdown to 'Most Downloads', or an alphabetical sort.
CLI tools
You can use either the
dotnet
CLI or the nuget.exe
CLI to support NuGet features in the IDE. The dotnet
CLI is installed with some Visual Studio workloads, such as .NET Core. The nuget.exe
CLI must be installed separately as described earlier.The two NuGet CLI tools are
dotnet.exe
and nuget.exe
. See feature availability for a comparison.- To target .NET Core or .NET Standard, use the dotnet CLI. The
dotnet
CLI is required for the SDK-style project format, which uses the SDK attribute. - To target .NET Framework (non-SDK-style project only), use the
nuget.exe
CLI. If the project is migrated frompackages.config
to PackageReference, use the dotnet CLI.
dotnet.exe CLI
The .NET Core 2.0 CLI,
dotnet.exe
, works on all platforms (Windows, Mac, and Linux) and provides core NuGet features such as installing, restoring, and publishing packages. dotnet
provides direct integration with .NET Core project files (such as .csproj
), which is helpful in most scenarios. dotnet
is also built directly for each platform and does not require you to install Mono.Installation:
- On developer computers, install the .NET Core SDK. Starting in Visual Studio 2017, the dotnet CLI is automatically installed with any .NET Core related workloads.
- For build servers, follow the instructions on Using .NET Core SDK and tools in Continuous Integration.
To learn how to use basic commands with the dotnet CLI, see Install and use packages using the dotnet CLI.
nuget.exe CLI
The
nuget.exe
CLI, nuget.exe
, is the command-line utility for Windows that provides all NuGet capabilities; it can also be run on Mac OSX and Linux using Mono with some limitations.To learn how to use basic commands with the
nuget.exe
CLI, see Install and use packages using the nuget.exe CLI.Installation:
Windows
Note
NuGet.exe 5.0 and later require .NET Framework 4.7.2 or later to execute.
- Visit nuget.org/downloads and select NuGet 3.3 or higher (2.8.6 is not compatible with Mono). The latest version is always recommended, and 4.1.0+ is required to publish packages to nuget.org.
- Each download is the
nuget.exe
file directly. Instruct your browser to save the file to a folder of your choice. The file is not an installer; you won't see anything if you run it directly from the browser. - Add the folder where you placed
nuget.exe
to your PATH environment variable to use the CLI tool from anywhere.
macOS/Linux
Behaviors may vary slightly by OS distribution.
- Install Mono 4.4.2 or later. Is microsoft project 2010 available for mac.
- Execute the following command at a shell prompt:
- Create an alias by adding the following script to the appropriate file for your OS (typically
~/.bash_aliases
or~/.bash_profile
): - Reload the shell. Test the installation by entering
nuget
with no parameters. NuGet CLI help should display.
Microsoft Packages For Smithsonian For Mac 2016
Tip
Microsoft Packages For Smithsonian For Mac Download
Use
nuget update -self
on Windows to update an existing nuget.exe to the latest version.Note
The latest recommended NuGet CLI is always available at
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
. For compatibility purposes with older continuous integration systems, a previous URL, https://nuget.org/nuget.exe
currently provides the deprecated 2.8.6 CLI tool.Feature availability
Feature | dotnet CLI | nuget CLI (Windows) | nuget CLI (Mono) | Visual Studio (Windows) | Visual Studio for Mac |
---|---|---|---|---|---|
Search packages | ✔ | ✔ | ✔ | ✔ | |
Install/uninstall packages | ✔ | ✔(1) | ✔ | ✔ | ✔ |
Update packages | ✔ | ✔ | ✔ | ✔ | |
Restore packages | ✔ | ✔ | ✔(2) | ✔ | ✔ |
Manage package feeds (sources) | ✔ | ✔ | ✔ | ✔ | |
Manage packages on a feed | ✔ | ✔ | ✔ | ||
Set API keys for feeds | ✔ | ✔ | |||
Create packages(3) | ✔ | ✔ | ✔(4) | ✔ | |
Publish packages | ✔ | ✔ | ✔ | ✔ | |
Replicate packages | ✔ | ✔ | |||
Manage global-package and cache folders | ✔ | ✔ | ✔ | ||
Manage NuGet configuration | ✔ | ✔ |
(1) Does not affect project files; use
dotnet.exe
instead.(2) Works only with
packages.config
file and not with solution (.sln
) files.(3) Various advanced package features are available through the CLI only as they aren't represented in the Visual Studio UI tools.
(4) Works with
.nuspec
files but not with project files.Upcoming Features
If you'd like to preview upcoming NuGet features, install a Visual Studio Preview, which works side-by-side with stable releases of Visual Studio. To report problems or share ideas for previews, open an issue on the NuGet GitHub repository.
Related topics
Developers working on Windows can also explore the NuGet Package Explorer, an open-source, stand-alone tool to visually explore, create, and edit NuGet packages. It's very helpful, for example, to make experimental changes to a package structure without rebuilding the package.
-->Applies to:Office for Mac, Office 2019 for Mac, Office 2016 for Mac
There are two basic ways that you, as an admin, can deploy Office for Mac to users in your organization:
- Provide your users with the installer package file, and have them install Office for Mac for themselves
- Download the installer package file to your local network, and then use your software distribution tools to deploy Office for Mac to your users
If you have an Office 365 plan, you can provide your users with instructions on how to download and install Office for Mac for themselves. To install Office for Mac, a user has to be administrator on the Mac or know an administrator account name and password.
But, if you deploy Office for Mac for your users, you have more control over the deployment, including which users get Office for Mac and when. Microsoft word 2016 not responding windows 10. To plan your deployment, review the following information.
Download Office for Mac to your local network
The easiest way to download Office for Mac, and ensure you're always getting the most current version and build, is to download directly from the Office Content Delivery Network (CDN) on the internet. Here are the links to the installer packages for the Office suite, which contains all the applications:
- Office for Mac (for Office 365 plans)
- Office 2019 for Mac (for retail or volume licensed versions)
- Office 2016 for Mac (for retail or volume licensed versions)
Note
- Installer and update packages for individual applications are also available on the Office CDN. For links to those, see Most current packages for Office for Mac.
- The same installer package is used for Office for Mac and Office 2019 for Mac. How you activate the product determines whether you get the features for Office for Mac or the features for Office 2019 for Mac.
- Unlike Office 2016 for Mac, the installer package for Office 2019 for Mac isn't available on the Volume Licensing Service Center (VLSC).
Deploy Office for Mac to users in your organization
Office for Mac uses the Apple Installer technology for installation. That means you can use the software distribution tools that you normally use to deploy software to Mac users. Some of the most common tools are Jamf Pro, Munki, and AutoPkg. You can also use Apple Remote Desktop and AppleScript.
Important
There are changes in Office for Mac to improve security, including implementing Apple app sandboxing guidelines. These changes mean that you can't customize the app bundle before or after you deploy Office. Don't add, change, or remove files in an app bundle. For example, even if you don't need the French language resource files for Excel, don't delete them. This change prevents Excel from starting. Even though you can't customize app bundles, you can configure preferences for each app.
Additional deployment information for Office for Mac
Whichever deployment method you decide to use, the following information can help you plan your Office for Mac deployment.
- What's new: Before you deploy, review the information about what's new for admins in Office for Mac. This includes information about system requirements, language support, and new features.
- Side-by-side installation: You can't have Office 2016 for Mac and Office 2019 for Mac installed on the same computer. Also, you can't have Office for Mac (from an Office 365 plan) along with either Office 2016 for Mac or Office 2019 for Mac (both of which are one-time purchase versions) installed on the same computer.
- Deploying individual apps: Installer package files for individual applications are available on the Office Content Delivery Network (CDN). For links to those, see Most current packages for Office for Mac.
- Activation: To use Office for Mac, it needs to be activated. Before you deploy, review the information about how activation works in Office for Mac.
- Uninstalling: If you need to uninstall Office for Mac, you can follow these steps to completely remove Office for Mac. Unfortunately, there is no program to uninstall Office for Mac automatically.
- Office for Mac 2011: Support for Office for Mac 2011 ended on October 10, 2017. All of your Office for Mac 2011 apps will continue to function. But, you could expose yourself to serious and potentially harmful security risks. To completely remove Office for Mac 2011, follow these steps.
- Upgrading to Office 2019 for Mac: If you're a volume licensed customer, you can upgrade to Office 2019 for Mac without uninstalling Office 2016 for Mac. You just need to download the 2019 version of the Volume License (VL) Serializer from the Volume Licensing Service Center (VLSC) and deploy it to each computer running Office 2016 for Mac. If you need to go back to Office 2016 for Mac after you've upgraded, follow these steps.
- Version numbers Version numbers of 16.17 or higher for retail or volume licensed installs indicate you have Office 2019 for Mac. Office 2016 for Mac has version numbers of 16.16 or lower. Since the 'major' version (16) hasn't changed between Office 2016 for Mac and Office 2019 for Mac, application settings, including policies, preferences, and preference domains are similar between the two versions. Also, add-ins and other extensibility solutions that are compatible with Office 2016 for Mac will most likely be compatible with Office 2019 for Mac or will require minimal testing.