. Runs on any Mac with Yosemite or above. Looks and feels just like MS Project, but on your Mac!. Supports files created in versions of MS Project, going all the way back to Microsoft Project 98. Integrated with all major cloud providers, such as Google Drive, iCloud, One Drive, Box, Dropbox, SharePoint Online and Project Online. Ready for large corporate Mac deployments. Teamwork (formerly known as Teamwork Projects) really pushes the boat out when it.
- Microsoft project for mac free download - Microsoft Virtual PC for Mac 7.0.3 Update, Parallels Desktop for Mac, Microsoft Virtual PC for Mac Update, and many more programs.
- Microsoft AutoUpdate makes sure your copy of Office will always be up-to-date with the latest security fixes and improvements. If you are a Microsoft 365 subscriber, you'll also receive the newest features and tools. Check for updates and install. Open an Office app such as Word, then on the top menu, click Help Check for Updates.
- More than half of our users are on Mac’s and use Microsoft Remote Desktop. We have found Version 10 much harder to setup on users desktops because unlike the prior version where most of the information was in one place - now its spread around via access to dropdowns and in various locations.
In this article, you'll learn how to install .NET Core on macOS. .NET Core is made up of the runtime and the SDK. The runtime is used to run a .NET Core app and may or may not be included with the app. The SDK is used to create .NET Core apps and libraries. The .NET Core runtime is always installed with the SDK.
The latest version of .NET Core is 3.1.
Supported releases
The following table is a list of currently supported .NET Core releases and the versions of macOS they're supported on. These versions remain supported either the version of .NET Core 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.
Operating System | .NET Core 2.1 | .NET Core 3.1 | .NET 5 Preview |
---|---|---|---|
macOS 10.15 'Catalina' | ✔️ 2.1 (Release notes) | ✔️ 3.1 (Release notes) | ✔️ 5.0 Preview (Release notes) |
macOS 10.14 'Mojave' | ✔️ 2.1 (Release notes) | ✔️ 3.1 (Release notes) | ✔️ 5.0 Preview (Release notes) |
macOS 10.13 'High Sierra' | ✔️ 2.1 (Release notes) | ✔️ 3.1 (Release notes) | ✔️ 5.0 Preview (Release notes) |
macOS 10.12 'Sierra' | ✔️ 2.1 (Release notes) | ❌ 3.1 (Release notes) | ❌ 5.0 Preview (Release notes) |
Unsupported releases
The following versions of .NET Core 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 Core. 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 three different runtimes you can install on macOS:
ASP.NET Core runtime
Runs ASP.NET Core apps. Includes the .NET Core runtime.
Runs ASP.NET Core apps. Includes the .NET Core runtime.
.NET Core 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 Core apps.
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 Core apps.
SDK information
The SDK is used to build and publish .NET Core apps and libraries. Installing the SDK includes both runtimes: ASP.NET Core and .NET Core.
Dependencies
.NET Core is supported on the following macOS releases:
.NET Core Version | macOS | Architectures | |
---|---|---|---|
3.1 | High Sierra (10.13+) | x64 | More information |
3.0 | High Sierra (10.13+) | x64 | More information |
2.2 | Sierra (10.12+) | x64 | More information |
2.1 | Sierra (10.12+) | x64 | More information |
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 Core runtime, .NET Core SDK, and software created with .NET Core.
The installers for .NET Core (both runtime and SDK) versions 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 Core (and your .NET Core apps), see Working with macOS Catalina Notarization.
libgdiplus
.NET Core 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
macOS has standalone installers that can be used to install the .NET Core 3.1 SDK:
![Legend Legend](/uploads/1/1/9/8/119873869/721837464.jpg)
Download and manually install
As an alternative to the macOS installers for .NET Core, 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 Core 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 preview 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 Core and then ensure .NET Core is in PATH.To extract the runtime and make the .NET Core CLI commands available at the terminal, first download a .NET Core 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 command to extract the runtime:
Use the following command to extract the SDK:
Tip
The preceding
export
commands only make the .NET Core 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 Core SDK when the .NET Core workload is selected. To get started with .NET Core development on macOS, see Install Visual Studio 2019 for Mac. For the latest release, .NET Core 3.1, you must use the Visual Studio for Mac 8.4.
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 Core installer like Visual Studio does, adding .NET Core support is simple.
- Download and install Visual Studio Code.
- Download and install the .NET Core SDK.
- 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.Microsoft Project For Mac Os X
Note
The command above installs the ASP.NET Core runtime for maximum compatability. The ASP.NET Core runtime also includes the standard .NET Core 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.
.NET Core can run in a Docker container. Official .NET Core 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.
Microsoft Project is the best project, portfolio, and resource management solution—but it’s not available on macOS®. However, with Parallels Desktop® for Mac, Apple® users can use a Windows virtual machine (VM) to run Microsoft Project on Mac®.
Getting started with running MS Project on macOS is easy:
- Download a trial of Parallels Desktop.
- Set up a Windows 10 VM. It’s very easy to buy a new Windows 10 license inside Parallels Desktop. (You can also use an existing Windows 10 license key.)
- Purchase Microsoft Project and download the .exe file in your Windows 10 VM.
- Start using Microsoft Project to get your job done!
Parallels Desktop is the #1 virtualization solution to run Windows, Linux, and other popular operating systems on Mac. Virtualization of a Windows OS on Mac has endless benefits, including:
- Low cost in comparison to buying a second computer
- Minimized or eliminated downtime
- Increased productivity
- Faster backups
- Easy to recover or migrate to additional Mac devices
- Economic use of energy
- Eco-friendly choice to minimize the amount of electronic waste a single user produces.
If you’re still deciding if Parallels Desktop is right for you, continue reading to understand how a program manager utilizes virtualization to run Microsoft Project.
Microsoft Project Management For Mac Os
As a self-employed program manager, Tim specializes in large-scale data migrations and the development of sustainable business intelligence (BI) and analytic solutions. He has a wealth of experience in both IT and capital asset delivery, as well as general management, operational, and strategic roles in asset-intensive industries and regulation.
Ms Project For Mac Os
Like most consultants, Tim needs slick and stable IT to allow him to focus on the real issues. He doesn’t want IT issues to constantly be distracting him. Parallels Desktop offers a reliable platform that allows him to deliver.
As an avid personal user of Apple products, Tim also wished to migrate his work life to Mac. However, for most clients he needed to use Microsoft Project as a Gantt chart management tool. Being able to manage multi-project plans is an essential element for any program manager. Unfortunately, Microsoft Project is one of the few pieces of Microsoft software that has not been developed to run on macOS.
After online research, Tim concluded that the only successful way to use Microsoft Project on a Mac was through a Windows virtual machine. He discussed the issue directly with Apple, and they recommended Parallels Desktop as a solution.
Following a very simple installation of Parallels, Tim can now use Microsoft Project natively within a Windows environment on his MacBook Pro®. This means there’s no translation between products claiming to act as a Microsoft Project editor—quite simply, he’s running a Windows version of Microsoft Project on his Mac. It has proved to be an excellent solution for Tim.
Tim wholeheartedly recommends Parallels Desktop, which he has now been using successfully for several months. Installation was simple, and there are many configuration options that can be changed. (For example, the amount of memory dedicated to the Apple or Windows operating system.) This gives greater flexibility to the user. Tim hasn’t had any issues with Parallels Desktop at all, and the product is extremely stable in every way. Tim also added that Parallels® Toolbox (which comes included with Parallels Desktop) has been useful. He particularly likes the disk cleaning tool, which ensures his laptop is always operating efficiently.
If you’d like to use Parallels Desktop to run popular Windows programs on Mac (without rebooting!), download a free 14-day trial.