Skinny downloading

1. Install The Azure CLI For MacOS Microsoft Docs
2. Brewery Mac Os Catalina

Homebrew is an open-source package manager for macOS that offers an easy way to install software and tolls through the command line. If you are a coder, developer, Terminal lover, or more tech-savvy than an average Mac user, you can use Homebrew to simplify software installation on your Mac.

Homebrew lets you use commands to download and install Python, Ruby, MongoDB, PHP, Git, Node.js, cask, colordiff, Nmap, and other Unix command-line utilities. In this guide, I’ll show you how to install Homebrew in macOS Catalina or M1 Mac.

Homebrew is a package manager for OS X. Open Terminal and install Homebrew with: $ ruby -e '$ (curl -fsSkL raw.github.com/mxcl/homebrew/go)' Once the installation is successful, you can run the following command to check your environment. Automated updates for the core OS has been available for several years now on Macs, and Apple has added the ability to update automatically apps you have added from the AppStore as well. However, if you have installed open source apps with Brew, chances are that you may forget to update them regularly.

Requirements to install Homebrew on Mac

• A 64-bit Intel or Apple Silicon M1 CPU
• macOS Mojave (10.14) or later
• Command Line Tools (CLT) for Xcode (steps 1 and 2 below)
  Note: Some formulae require full Xcode installation.
• A Bourne-compatible shell for installation (e.g., bash or zsh)
• Administrator access on Mac
• Internet connectivity

For some finer requirement details, please see the official page.

Once you satisfy the above requirements, see how to install Homebrew on macOS.

How to install Homebrew on macOS Catalina or M1 Mac

1. Open Terminal and enter this command xcode-select --install
2. Click Install from the popup. Go through the T&C and click Agree if you do. Let the download complete.
3. To install Homebrew, enter the following command in the Terminal. /usr/bin/ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)'
4. You will have to enter your Mac’s password once. After that, the downloading and installation will begin. The total download size is around 400MB. It will take some time.

Verify Homebrew installation in macOS

1. Open Terminal and type brew -v
2. You will see the version of Homebrew installed on your Mac.

Tip: brew doctor lets you know about Homebrew status, issues, and updates, if available or required.

Now that you have installed Homebrew, let’s see how to use it.

How to use Homebrew to install a package on Mac

• To see the full list of packages: brew formulae
• To search a software package: brew search packagename
• Get information about a package: brew info packagename
• To download and install: brew install packagename
  For example, if I have to install speedtest-cli, here is how the command looks: brew install speedtest-cli
  After installation, enter speedtest-cli in the Terminal to run this command.
• Pro Tip: You can install not only command-line apps but also GUI (Graphical User Interface) apps via Homebrew. For this, use brew install --cask app-name. For example, brew install --cask firefox or brew install --cask google-chrome You can see the full list here.
• To see all the apps installed by Homebrew on your Mac: brew list
  Tip: Packages are usually installed in this folder: /usr/local/Cellar
  In case you do not find this folder, enter brew --prefix in the Terminal to see the folder location.
• To update the package: brew update packagename
• For removing an installed package: brew remove packagename
• To know what else you can do: man brew

How to update or remove Homebrew from your Mac

At times, Homebrew is updated automatically when you run commands. But you can also update it manually by entering brew update in the Terminal.

In case you no longer need Homebrew, run the following command to uninstall Homebrew and all the installed packages.
ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)'

Loving the ease and simplicity of Homebrew!

I hope the above guide helped you download, install, and use Homebrew. Once you start using it, there is no going back. Finally, I would like to tell you about four handy command-line programs I love.

• Youtube-dl: This lets me download videos from YouTube and other places. More info.
• speedtest-cli: I can see my download and upload speed via this. More info.
• imagemagick: Lets me convert an image to another format and make simple edits. More info.
• wifi-password: This brilliant yet straightforward command shows me the Wi-Fi password of the currently connected network. Super handy!

You will also love to read:

In this article, you'll learn how to install .NET on macOS. .NET is made up of the runtime and the SDK. The runtime is used to run a .NET app and may or may not be included with the app. The SDK is used to create .NET apps and libraries. The .NET runtime is always installed with the SDK.

The latest version of .NET is 5.0.

Supported releases

The following table is a list of currently supported .NET releases and the versions of macOS they're supported on. These versions remain supported either the version of .NET reaches end-of-support.

• A ✔️ indicates that the version of .NET Core is still supported.
• A ❌ indicates that the version of .NET Core isn't supported.

Unsupported releases

The following versions of .NET are ❌ no longer supported. The downloads for these still remain published:

• 3.0 (Release notes)
• 2.2 (Release notes)
• 2.0 (Release notes)

Runtime information

The runtime is used to run apps created with .NET. When an app author publishes an app, they can include the runtime with their app. If they don't include the runtime, it's up to the user to install the runtime.

There are two different runtimes you can install on macOS:

• ASP.NET Core runtime
  Runs ASP.NET Core apps. Includes the .NET runtime.

• .NET runtime
  This runtime is the simplest runtime and doesn't include any other runtime. It's highly recommended that you install ASP.NET Core runtime for the best compatibility with .NET apps.

SDK information

The SDK is used to build and publish .NET apps and libraries. Installing the SDK includes both runtimes: ASP.NET Core and .NET.

Dependencies

.NET is supported on the following macOS releases:

Beginning with macOS Catalina (version 10.15), all software built after June 1, 2019 that is distributed with Developer ID, must be notarized. This requirement applies to the .NET runtime, .NET SDK, and software created with .NET.

The runtime and SDK installers for .NET 5.0 and .NET Core 3.1, 3.0, and 2.1, have been notarized since February 18, 2020. Prior released versions aren't notarized. If you run a non-notarized app, you'll see an error similar to the following image:

For more information about how enforced-notarization affects .NET (and your .NET apps), see Working with macOS Catalina Notarization.

libgdiplus

.NET applications that use the System.Drawing.Common assembly require libgdiplus to be installed.

An easy way to obtain libgdiplus is by using the Homebrew ('brew') package manager for macOS. After installing brew, install libgdiplus by executing the following commands at a Terminal (command) prompt:

Install with an installer

Install The Azure CLI For MacOS Microsoft Docs

macOS has standalone installers that can be used to install the .NET 5.0 SDK:

Download and manually install

As an alternative to the macOS installers for .NET, you can download and manually install the SDK and runtime. Manual install is usually performed as part of continuous integration testing. For a developer or user, it's generally better to use an installer.

If you install .NET SDK, you don't need to install the corresponding runtime. First, download a binary release for either the SDK or the runtime from one of the following sites:

• ✔️ .NET 5.0 downloads
• ✔️ .NET Core 3.1 downloads
• ✔️ .NET Core 2.1 downloads

Next, extract the downloaded file and use the export command to set variables used by .NET and then ensure .NET is in PATH.

To extract the runtime and make the .NET CLI commands available at the terminal, first download a .NET binary release. Then, open a terminal and run the following commands from the directory where the file was saved. The archive file name may be different depending on what you downloaded.

Use the following commands to extract the runtime or SDK that you downloaded. Remember to change the DOTNET_FILE value to your file name:

Tip

The preceding export commands only make the .NET CLI commands available for the terminal session in which it was run.

You can edit your shell profile to permanently add the commands. There are a number of different shells available for Linux and each has a different profile. For example:

• Bash Shell: ~/.bash_profile, ~/.bashrc
• Korn Shell: ~/.kshrc or .profile
• Z Shell: ~/.zshrc or .zprofile

Edit the appropriate source file for your shell and add :$HOME/dotnet to the end of the existing PATH statement. If no PATH statement is included, add a new line with export PATH=$PATH:$HOME/dotnet.

Also, add export DOTNET_ROOT=$HOME/dotnet to the end of the file.

This approach lets you install different versions into separate locations and choose explicitly which one to use by which application.

Install with Visual Studio for Mac

Visual Studio for Mac installs the .NET SDK when the .NET workload is selected. To get started with .NET development on macOS, see Install Visual Studio 2019 for Mac.

Install alongside Visual Studio Code

Visual Studio Code is a powerful and lightweight source code editor that runs on your desktop. Visual Studio Code is available for Windows, macOS, and Linux.

While Visual Studio Code doesn't come with an automated .NET installer like Visual Studio does, adding .NET support is simple.

1. Download and install Visual Studio Code.
2. Download and install the .NET SDK.
3. Install the C# extension from the Visual Studio Code marketplace.

Install with bash automation

The dotnet-install scripts are used for automation and non-admin installs of the runtime. You can download the script from the dotnet-install script reference page.

The script defaults to installing the latest long term support (LTS) version, which is .NET Core 3.1. You can choose a specific release by specifying the current switch. Include the runtime switch to install a runtime. Otherwise, the script installs the SDK.

Note

The previous command installs the ASP.NET Core runtime for maximum compatability. The ASP.NET Core runtime also includes the standard .NET runtime.

Docker

Containers provide a lightweight way to isolate your application from the rest of the host system. Containers on the same machine share just the kernel and use resources given to your application.

Brewery Mac Os Catalina

.NET can run in a Docker container. Official .NET Docker images are published to the Microsoft Container Registry (MCR) and are discoverable at the Microsoft .NET Core Docker Hub repository. Each repository contains images for different combinations of the .NET (SDK or Runtime) and OS that you can use.

Microsoft provides images that are tailored for specific scenarios. For example, the ASP.NET Core repository provides images that are built for running ASP.NET Core apps in production.

For more information about using .NET Core in a Docker container, see Introduction to .NET and Docker and Samples.

Next steps

• How to check if .NET Core is already installed.
• Working with macOS Catalina notarization.
• Tutorial: Get started on macOS.
• Tutorial: Create a new app with Visual Studio Code.
• Tutorial: Containerize a .NET Core app.