Hunterni332

Mattermost desktop applications are available for Windows, Mac, and Linux operating systems. They support all the features of the web experience, plus:

• Connect to multiple Mattermost servers from a single interface, and switch with shortcut keys.

• Auto-start Mattermost when a user logs into their machine.

• (Windows) Add Mattermost to Start menu, Taskbar, and System Tray.

• (Windows/Mac) Deep link to the desktop app via mattermost:// protocol if app is already installed.

• (Mac) Add Mattermost to the Dock.

• (Linux) DesktopEntry for the application to more easily integrate into a desktop environment.

Below is a list of additional resources:

• Contributor’s guide (coming soon)

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: brew update brew install mono-libgdiplus Install with an installer. MacOS has standalone installers that can be used to install the.NET 5.0 SDK. This exercise was to get a running MacOS Catalina VM instance running on VMware. I first wrote this for Catalina Beta but afte rthe official release, a couple things changed. So now it is how to install Catalina on ESXi 6.7. I am using a 2013 Mac Pro with VMWare 6.7 U2 installed. I have High Sierra and Mojave VMs running on the host.

You can download the apps directly from our downloads page. You may also use the following installation guides for Windows, Mac, and Linux.

Contents

1. Download the latest version of the Mattermost desktop app:

2. From the Downloads folder right-click on the file mattermost-desktop-setup-4.6.2-win.exe and select Open.

This will start an installer for the app. Once finished, the Mattermost desktop app will open automatically.

Download the latest version of the Mattermost desktop app MSI installer (Beta):

• MSI for 64-bit version of Windows

• MSI for 32-bit version of Windows

See here for instructions on installing the Mattermost desktop app via an MSI installer and configuring supported Group Policies.

The following Group Policies are available:

1. Download the latest version of the Mattermost desktop app.

2. Double-click the download to open the disk image.

3. Drag the Mattermost application to the Applications folder.

Homebrew users can install with brewinstall--caskmattermost.

1. Download the latest version of the Mattermost desktop app:

• 64-bit systems: mattermost-desktop-4.6.2-linux-x64.tar.gz

• 32-bit systems: mattermost-desktop-4.6.2-linux-ia32.tar.gz

2. Extract the archive to a convenient location. You can then execute mattermost-desktop, which is located inside the extracted directory.

3. To create a Desktop launcher, open the file README.md and follow the instructions in the Desktop launcher section.

Unofficial, community-driven .deb packages are available.

1. Download the latest version of the Mattermost Desktop App:

• 64-bit systemsmattermost-desktop-4.6.2-linux-amd64.deb

• 32-bit systemsmattermost-desktop-4.6.2-linux-i386.deb

2. At the command line, execute one of the following commands depending on the package that you downloaded:

• 64-bit systems

  sudodpkg-imattermost-desktop-4.6.2-linux-amd64.deb

• 32-bit systems

  sudodpkg-imattermost-desktop-4.6.2-linux-i386.deb

3. To run Mattermost, open Dash (located at the top left corner), enter mattermost, then click the Mattermost icon.

To install the Desktop client on Arch Linux, see the Mattermost page on the Arch Linux wiki.

A snap is available for systems that have Snapcraft installed. Snapcraft is installed by default on Ubuntu 16.04 and later, but for most other Linux distributions you can install it manually. To install Snapcraft, see Install snapd on the Snapcraft website.

1. At the command line, execute the following command:

2. To run Mattermost, open Dash (located at the top left corner), enter mattermost, then click the Mattermost icon.

The app data might be corrupted. Remove all the files in %LOCALAPPDATA%mattermost, then try reinstalling the app.

On macOS Catalina, this dialog can be triggered if the Mac Archive Utility is the default method for decompressing files. In this case using a third-party tool such as Keka or Unarchiver may resolve the problem.

1. First, make sure you have installed the latest desktop app version from our website. Check your app version from Help > Version.

2. Try to clear cache and reload the app from View > Clear Cache and Reload or use CTRL/CMD+SHIFT+R.

3. Quit the app and restart it to see if the issue clears.

4. Disable GPU hardware acceleration from File > Settings on Windows and Linux or Mattermost > Settings on macOS, and unselect Use GPU hardware acceleration.

5. If you are using a special video driver, such as Optimus, try disabling it to see if the problem is resolved.

If none of the above steps resolve the issue, please open a new ticket in the Mattermost Troubleshooting Forum.

This issue can occur on Windows in a multiple-monitor setup. When you disconnect the monitor that Mattermost is displayed on, Mattermost continues to display at screen coordinates that no longer exist.

To resolve this issue, you can reset the desktop app screen location by deleting the screen location file. When the file is not present, the desktop app displays on the primary monitor by default.

To reset the desktop app screen location

1. If the desktop app is running, right-click the Mattermost icon in the task bar and click Close Window.

2. Open Windows File Explorer, and navigate to the %APPDATA%Mattermost folder.

3. Delete the file bounds-info.json.

This issue can occur when localStorage has an unexpected state. To resolve the issue:

• Windows: Open Windows File Explorer, navigate to the %APPDATA%Mattermost folder, then delete the LocalStorage folder.

• Mac: Open Finder, navigate to the ~/Library/ApplicationSupport/Mattermost folder, then delete the LocalStorage folder.

• Linux: Open the File Manager, navigate to the ~/.config/Mattermost folder, then delete the LocalStorage folder.

This issue can occur after a crash or unexpected shutdown of the desktop app that causes the app data to be corrupted. To resolve the issue:

• Windows: Open Windows File Explorer, navigate to the``%APPDATA%Mattermost`` folder, then delete the IndexedDB folder and the Cookies and Cookies-journal files.

• Mac: Open Finder, navigate to the ~/Library/ApplicationSupport/Mattermost folder, then delete the IndexedDB folder and the Cookies and Cookies-journal files.

• Linux: Open the file manager, navigate to the ~/.config/Mattermost folder, then delete the IndexedDB folder and the Cookies and Cookies-journal files.

Clicking Show Details on the dialog provides logs. Ways to resolve the issue:

1. Clear the cache via View > Clear Cache and Reload or CTRL+SHIFT+R.

2. Go to App Settings via File > Settings or CTRL+COMMA and unselect hardware acceleration.

Mac Catalina Brew Update

Append Mattermost.exe; to the Registry Key HKLMSYSTEMCurrentControlSetServicesCtxUviUviProcessExcludes and reboot the system.

For further assistance, review the Troubleshooting forum for previously reported errors, or join the Mattermost user community for troubleshooting help.

When reporting bugs found in the Mattermost desktop app, it is helpful to include the contents of the Developer Tools Console along with the information on this page. To access the Developer Tools Console, follow these instructions:

1. In the menu bar, go to View > Toggle Developer Tools.

2. Select the Console tab.

3. Right-click the log window and select Save As.

4. Save the file and then send it along with a description of your issue.

5. Go to View > Toggle Developer Tools to disable the Developer Tools.

You can open an additional set of developer tools for each server you have added to the desktop app. The tools can be opened by pasting this command in the Developer Tools Console you opened with the steps described above:

document.getElementsByTagName('webview')[0].openDevTools();

Note that if you have more than one server added to the desktop client, you need to change the 0 to the number corresponding to the server you want to open in the Developer Tools Console, starting with 0 from the left.

To submit an improvement or correction to this documentation, click Edit at the top of this page.

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

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

Macos Catalina Homebrew

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.

.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.