-->

Microsoft Office Home and Student 2019 (1 Mac) - Previous Gallery Image; Microsoft Office Home and Student 2019 (1 Mac) - Next Gallery Image. Word, Excel, Outlook and PowerPoint in Microsoft 365 are getting a boost in their image and icon libraries with the addition of stock images or ‘premium creative content’. We’re told there are ‘over 8,000’ images and icons with ‘more to come’.

Applies to: Configuration Manager (current branch)

Keep the following considerations in mind when you create and deploy applications for Mac computers.

See and discover other items: Best microsoft office for pc, microsoft 365 office, microsoft office mac 2019, MS Office 2019, Best windows software for pc, 2013 MacBooks. Microsoft Activex Data Objects Library For Mac Download Setting up an ADO project and writing ADO code is similar whether you use Visual Basic or Visual Basic for Applications. This topic addresses using ADO with both Visual Basic and Visual Basic for Applications and notes any differences.

Important

The procedures in this topic cover information about deploying applications to Mac computers on which you installed the Configuration Manager client. Mac computers that you enrolled with Microsoft Intune do not support application deployment.

General considerations

You can use Configuration Manager to deploy applications to Mac computers that run the Configuration Manager Mac client. The steps to deploy software to Mac computers are similar to the steps to deploy software to Windows computers. However, before you create and deploy applications for Mac computers that are managed by Configuration Manager, consider the following:

• Before you can deploy Mac application packages to Mac computers, you must use the CMAppUtil tool on a Mac computer to convert these applications into a format that can be read by Configuration Manager.

• Configuration Manager does not support the deployment of Mac applications to users. Instead, these deployments must be made to a device. Similarly, for Mac application deployments, Configuration Manager does not support the Pre-deploy software to the user's primary device option on the Deployment Settings page of the Deploy Software Wizard.

• Mac applications support simulated deployments.

• You cannot deploy applications to Mac computers that have a purpose of Available.

• The option to send wake-up packets when you deploy software is not supported for Mac computers.

• Mac computers do not support Background Intelligent Transfer Service (BITS) for downloading application content. If an application download fails, it is restarted from the beginning.

• Configuration Manager does not support global conditions when you create deployment types for Mac computers.

Steps to create and deploy an application

The following table provides the steps, details, and information for creating and deploying applications for Mac computers.

Supplemental procedures to create and deploy applications for Mac computers

Use the following procedures to create and deploy applications for Mac computers that are managed by Configuration Manager.

Step 1: Prepare Mac applications for Configuration Manager

The process for creating and deploying Configuration Manager applications to Mac computers is similar to the deployment process for Windows computers. However, before you create Configuration Manager applications that contain Mac deployment types, you must prepare the applications by using the CMAppUtil tool. This tool is downloaded with the Mac client installation files. The CMAppUtil tool can gather information about the application, which includes detection data from the following Mac packages:

• Apple disk image (.dmg)

• Meta package file (.mpkg)

• macOS X installer package (.pkg)

• macOS X application (.app)

After it gathers application information, the CMAppUtil then creates a file with the extension .cmmac. This file contains the installation files for the Mac software and information about detection methods that can be used to evaluate whether the application is already installed. CMAppUtil can also process .dmg files that contain multiple Mac applications and create different deployment types for each application.

1. Copy the Mac software installation package to the folder on the Mac computer where you extracted the contents of the macclient.dmg file that you downloaded from the Microsoft Download Center.

2. On the same Mac computer, open a terminal window and navigate to the folder where you extracted the contents of the macclient.dmg file.

3. Navigate to the Tools folder and type the following command-line command:

   ./CMAppUtil<properties>

   For example, say you want to convert the contents of an Apple disk image file named MySoftware.dmg that's stored in the user's desktop folder into a cmmac file in the same folder. You also want to create cmmac files for all applications that are found in the disk image file. To do this, use the following command line:

   ./CMApputil –c /Users/<User Name>/Desktop/MySoftware.dmg -o /Users/<User Name>/Desktop -a

   Note

   The application name can't be more than 128 characters.

   To configure options for CMAppUtil, use the command-line properties in the following table:

   Property	More information
   -h	Displays the available command-line properties.
   -r	Outputs the detection.xml of the provided .cmmac file to stdout. The output contains the detection parameters and the version of CMAppUtil that was used to create the .cmmac file.
   -c	Specifies the source file to be converted.
   -o	Specifies the output path in conjunction with the –c property.
   -a	Automatically creates .cmmac files in conjunction with the –c property for all applications and packages in the disk image file.
   -s	Skips generating the detection.xml if no detection parameters are found and forces the creation of the .cmmac file without the detection.xml file.
   -v	Displays more detailed output from the CMAppUtil tool together with diagnostic information.

4. Ensure that the .cmmac file has been created in the output folder that you specified.

Create a Configuration Manager application that contains the Mac software

Use the following procedure to help you create an application for Mac computers that are managed by Configuration Manager.

1. In the Configuration Manager console, choose Software Library > Application Management > Applications.

2. On the Home tab, in the Create group, choose Create Application.

3. On the General page of the Create Application Wizard, select Automatically detect information about this application from installation files.

   Note

   If you want to specify information about the application yourself, select Manually specify the application information. For more information about how to manually specify the information, see How to create applications with Configuration Manager.

4. In the Type drop-down list, select Mac OS X.

5. In the Location field, specify the UNC path in the form <server><share><filename> to the Mac application installation file (.cmmac file) that will detect application information. Alternatively, choose Browse to browse to and specify the installation file location.

   Note

   You must have access to the UNC path that contains the application.

6. Choose Next.

7. On the Import Information page of the Create Application Wizard, review the information that was imported. If necessary, you can choose Previous to go back and correct any errors. Choose Next to proceed.

8. On the General Information page of the Create Application Wizard, specify information about the application such as the application name, comments, version, and an optional reference to help you reference the application in the Configuration Manager console.

   Note

   Some of the application information might already be on this page if it was previously obtained from the application installation files.

9. Choose Next, review the application information on the Summary page, and then complete the Create Application Wizard.

10. The new application is displayed in the Applications node of the Configuration Manager console.

Step 3: Create a deployment type for the Mac application

Use the following procedure to help you create a deployment type for Mac computers that are managed by Configuration Manager.

Note

If you automatically imported information about the application in the Create Application Wizard, a deployment type for the application might already have been created.

1. In the Configuration Manager console, choose Software Library > Application Management > Applications.

2. Select an application. Then, on the Home tab, in the Application group, choose Create Deployment Type to create a new deployment type for this application.

   Note

   You can also start the Create Deployment Type Wizard from the Create Application Wizard and from the Deployment Types tab of the <application name>Properties dialog box.

3. On the General page of the Create Deployment Type Wizard, in the Type drop-down list, select Mac OS X.

4. In the Location field, specify the UNC path in the form <server><share><filename> to the application installation file (.cmmac file). Alternatively, choose Browse to browse to and specify the installation file location.

   Note

   You must have access to the UNC path that contains the application.

5. Choose Next.

6. On the Import Information page of the Create Deployment Type Wizard, review the information that was imported. If necessary, choose Previous to go back and correct any errors. Choose Next to continue.

7. On the General Information page of the Create Deployment Type Wizard, specify information about the application such as the application name, comments, and the languages in which the deployment type is available.

   Note

   Some of the deployment type information might already be on this page if it was previously obtained from the application installation files.

8. Choose Next.

9. On the Requirements page of the Create Deployment Type Wizard, you can specify the conditions that must be met before the deployment type can be installed on Mac computers.

10. Choose Add to open the Create Requirement dialog box and add a new requirement.

    Note

    You can also add new requirements on the Requirements tab of the <deployment type name>Properties dialog box.

11. From the Category drop-down list, select that this requirement is for a device.

12. From the Condition drop-down list, select the condition that you want to use to assess whether the Mac computer meets the installation requirements. The contents of this list varies depending on the category that you select.

13. From the Operator drop-down list, choose the operator to use to compare the selected condition to the specified value to assess whether the user or device meets the installation requirements. The available operators vary depending on the selected condition.

14. In the Value field, specify the values to use with the selected condition and operator to assess whether the user or device meets in the installation requirement. The available values vary depending on the condition and operator that you select.

15. Choose OK to save the requirement rule and exit the Create Requirement dialog box.

16. On the Requirements page of the Create Deployment Type Wizard, choose Next.

17. On the Summary page of the Create Deployment Type Wizard, review the actions for the wizard to take. If necessary, choose Previous to go back and change deployment type settings. Choose Next to create the deployment type.

18. After the Progress page finishes, review the actions that have been taken, and then choose Close to complete the Create Deployment Type Wizard.

19. If you started this wizard from the Create Application Wizard, you will return to the Deployment Types page.

Deploy the Mac application

The steps to deploy an application to Mac computers are the same as the steps to deploy an application to Windows computers, except for the following differences:

• The deployment of applications to users is not supported.

• Deployments that have a purpose of Available are not supported.

• The Pre-deploy software to the user's primary device option on the Deployment Settings page of the Deploy Software Wizard is not supported.

• Because Mac computers do not support Software Center, the setting User notifications on the User Experience page of the Deploy Software Wizard is ignored.

• The option to send wake-up packets when you deploy software is not supported for Mac computers.

Note

You can build a collection that contains only Mac computers. To do so, create a collection that uses a query rule and use the example WQL query in the How to create queries topic.

For more information, see Deploy applications.

Step 5: Monitor the deployment of the Mac application

You can use the same process to monitor application deployments to Mac computers as you would to monitor application deployments to Windows computers.

For more information, see Monitor applications.

Image use in Visual Studio

Before creating artwork, consider making use of the 1,000+ images in the Visual Studio Image Library.

Types of images

• Icons. Small images that appear in commands, hierarchies, templates, and so on. The default icon size used in Visual Studio is a 16x16 PNG. Icons produced by the image service automatically generate the XAML format for HDPI support.

  Note

  While images are used in the menu system, you should not create an icon for every command. Consult Menus and Commands for Visual Studio to see whether your command should get an icon.

• Thumbnails. Images used in the preview area of a dialog, such as the New Project dialog.

• Dialog images. Images that appear in dialogs or wizards, either as descriptive graphics or message indicators. Use infrequently and only when necessary to illustrate a difficult concept or gain the user's attention (alert, warning).

• Animated images. Used in progress indicators, status bars, and operation dialogs.

• Cursors. Used to indicate whether an operation is allowed using the mouse, where an object may be dropped, and so on.

Icon design

Overview

Visual Studio uses modern-style icons, which have clean geometry and a 50/50 balance of positive/negative (light/dark), and use direct, understandable metaphors. Crucial icon design points center around clarity, simplification, and context.

• Clarity: focus on the core metaphor that gives an icon its meaning and individuality.

• Simplification: reduce the icon to its core meaning - get the theme across with just the necessary element(s) and no frills.

• Context: consider all aspects of an icon's role during concept development, which is crucial when deciding which elements constitute the icon's core metaphor.

  With icons, there are a number of design points to avoid:

• Don't use icons that signify UI elements except when appropriate. Choose a more abstract or symbolic approach when the UI element is neither common, evident, nor unique.

• Don't overuse common elements like documents, folders, arrows, and the magnifying glass. Use such elements only when essential to the icon's meaning. For example, the right-facing magnifying glass should indicate only Search, Browse, and Find.

• Although some legacy icon elements maintain the use of perspective, don't create new icons with perspective unless the element lacks clarity without it.

• Don't cram too much information into an icon. A simple image that can be easily recognized or learned as a recognizable symbol is much more useful than an overly complex image. An icon cannot tell the whole story.

Icon creation

Concept development

Visual Studio has within its UI a wide variety of icon types. Carefully consider the icon type during development. Don't use unclear or uncommon UI objects for your icon elements. Opt for the symbolic in these cases, such as with the Smart Tag icon. Note that the meaning of the abstract tag on the left is more obvious than the vague, UI-based version on the right:

There are instances in which standard, easily recognizable UI elements do work well for icons. Add Window is one such example:

Don't use a document as a base element unless it is essential to the icon's meaning. Without the document element on Add Document (below) the meaning is lost, whereas with Refresh the document element is unnecessary to communicate the meaning.

The concept of 'show' should be represented by the icon which best illustrates what is being shown, such as with the Show All Files example. A lens metaphor may be used to indicate the concept of 'view' if necessary, such as with the Resource View example.

The right-facing magnifying glass icon should represent only Search, Find, and Browse. The left-facing variant with the plus sign or minus sign should represent only zoom in/zoom out.

In tree views, do not use both the folder icon and a modifier. When available, use only the modifier.

Style details

Layout

Stack elements as shown for standard 16x16 icons:

Layout stack for 16x16 icons

Status notification elements are better used as standalone icons. There are contexts, however, in which a notification should be stacked on the base element, such as with the Task Complete icon:

Standalone notification icons

Task Complete icon

Project icons are typically .ico files that contain multiple sizes. Most 16x16 icons contain the same elements. The 32x32 versions have more details, including the project type when applicable.

VB Windows Control Library Project icons, 16x16 and 32x32

Center an icon within its pixel frame. If that is not possible, align the icon to the top and/or right of the frame.

Icon centered within the pixel frame

Icon aligned to the top right of the frame

Icon centered and aligned to the top of the frame

To achieve ideal alignment and balance, avoid obstructing the icon's base element with action glyphs. Place the glyph near the top left of the base element. When adding an additional element, consider the alignment and balance of the icon.

Ensure size parity for icons that share elements and are used in sets. Note that in the incorrect pairing, the circle and arrow are oversized and don't match.

Use consistent line and visual weights. Evaluate how the icon you are building compares to other icons by using a side-by-side comparison. Never use the entire 16x16 frame, use 15x15 or smaller. The negative-to-positive (dark-to-light) ratio should be 50/50.

Use simple, comparable shapes and complementary angles to build your elements without sacrificing element integrity. Use 45° or 90° angles where possible.

Perspective

Keep the icon clear and understandable. Use perspective and a light source only when necessary. Although using perspective on icon elements should be avoided, some elements are unrecognizable without it. In such cases, a stylized perspective communicates the element's clarity.

3-point perspective

1-point perspective

Most elements should be facing or angled to the right:

Use light sources only when adding necessary clarity to an object.

Use outlines only to enhance legibility or to better communicate the metaphor. The negative-positive (dark-light) balance should be 50/50.

Icon types

Shell and command bar icons consist of no more than three of the following elements: one base, one modifier, one action, or one status.

Examples of shell and command bar icons

Tool window command bar icons consist of no more than three of the following elements: one base, one modifier, one action, or one status.

Examples of tool window command bar icons

Tree view disambiguator icons consist of no more than three of the following elements: one base, one modifier, one action, or one status.

Examples of tree view disambiguator icons

State-based value taxonomy icons exist in the following states: active, active disabled, and inactive disabled.

Examples of state-based value taxonomy icons

IntelliSense icons consist of no more than three of the following elements: one base, one modifier, and one status.

Examples of IntelliSense icons

Small (16x16) project icons should have no more than two elements: one base and one modifier.

Examples of small (16x16) project icons

Large (32x32) project icons consist of no more than four of the following elements: one base, one to two modifiers, and one language overlay.

Examples of large (32x32) project icons

Production details

All new UI elements should be created using Windows Presentation Foundation (WPF) and all new icons for WPF should be in 32-bit PNG format. The 24-bit PNG is a legacy format that does not support transparency and is therefore not recommended for icons.

Save the resolution at 96 DPI.

File types

• 32-bit PNG: the preferred format for icons. A lossless data compression file format that can store a single raster (pixel) image. 32-bit PNG files support alpha-channel transparency, gamma correction, and interlacing.

• 32-bit BMP: for non-WPF controls. Also called XP or high color, 32-bit BMP is an RGB/A image format, a true-color image with an alpha-channel transparency. The alpha channel is a layer of transparency designated in Adobe Photoshop that is then saved within the bitmap as an additional (fourth) color channel. A black background is added during artwork production to all 32-bit BMP files to provide a quick visual cue about the color depth. This black background represents the area to be masked out in the UI.

• 32-bit ICO: for Project icons and Add Item. All ICO files are 32-bit true color with alpha-channel transparency (RGB/A). Because ICO files can store multiple sizes and color depths, Vista icons are often in an ICO format containing 16x16, 32x32, 48x48, and 256x256 image sizes. In order to display properly in Windows Explorer, ICO files must be saved-down to 24-bit and 8-bit color depths for each image size.

• XAML: for design surfaces and Windows adorners. XAML icons are vector-based image files that support scaling, rotating, filing, and transparency. They are not common in Visual Studio today but are becoming more popular because of their flexibility.

• SVG

• 24-bit BMP: for the Visual Studio command bar. A true-color RGB image format, 24-bit BMP is an icon convention that creates a layer of transparency by using magenta (R=255, G=0, B=255) as a color key for a knock-out transparency layer. In a 24-bit BMP, all magenta surfaces are displayed using the background color.

• 24-bit GIF: for the Visual Studio command bar. A true-color RGB image format that supports transparency. GIF files are often used in Wizard artwork and GIF animations.

Icon construction

The smallest icon size in Visual Studio is 16x16. The largest in common use is 32x32. Keep in mind not to fill up the entire 16x16, 24x24, or 32x32 frame when designing an icon. Legible, uniform icon construction is essential to user recognition. Adhere to the following points when building icons.

• Icons should be clear, understandable, and consistent.

• It is better to use the status notification elements as single icons and not to stack them on top of an icon base element. In certain contexts, the UI might require the status element to be paired with a base element.

• Project icons are usually .ico files that contain several sizes. Only the 16x16, 24x24, and 32x32 icons are being updated. Most 16x16 and 24x24 icons will contain the same elements. The 32x32 icons contain more details, including the project language type when applicable.

• For 32x32 icons, the base elements generally have a 2-pixel line weight. A 1- or 2-pixel line weight can be used for detail elements. Use your best judgment to determine which is more suitable.

• Have at least a 1-pixel spacing between elements for 16x16 and 24x24 icons. For 32x32 icons, use 2-pixel spacing between elements and between the modifier and base element.

  
  Element spacing for icons sized 16x16, 24x24, and 32x32

Color and accessibility

Visual Studio compliance guidelines require that all icons in the product pass the accessibility requirements for color and contrast. This is achieved through icon inversion, and when you are designing, you should be aware they will be inverted programmatically in the product.

For more information on using color in Visual Studio icons, see Using color in images.

Microsoft Office Image Library

Using color in images

Overview

Icons in Visual Studio are primarily monochromatic. Color is reserved to convey specific information and never for decoration. Color is used:

• to indicate an action

• to alert the user to a status notification

• to designate language affiliation

• to differentiate items within IntelliSense

Accessibility

Visual Studio compliance guidelines require that all icons checked into the product pass the accessibility requirements for color and contrast. Colors in the visual language palette have been tested and meet these requirements.

Color inversion for dark themes

In order to make icons appear with the correct contrast ratio in the Visual Studio dark theme, an inversion is applied programmatically. The colors in this guide have been chosen in part so that they invert correctly. Restrict your use of color to this palette, or you will get unpredictable results when the inversion is applied.

Examples of icons that have had their colors inverted

Base palette

All standard icons contain three base colors. Icons contain no gradients or drop shadows, with one or two exceptions for 3D-tool icons.

In addition to the base colors, each icon may contain one additional color from the extended palette.

Extended palette

Action modifiers

The four colors below indicate the types of actions required by action modifiers:

Examples

Green is used for positive action modifiers like 'Add,' 'Run,' 'Play,' and 'Validate.'

Red is used for negative action modifiers like 'Delete,' 'Stop,' 'Cancel,' and 'Close.'

Blue is applied to neutral action modifiers most commonly represented as arrows, like 'Open,' 'Next,' 'Previous,' 'Import,' and 'Export.'

Dark gold is primarily used for the 'New' modifier.

Special cases

In special cases, a colored action modifier may be used independently as a standalone icon. The color used for the icon reflects the actions that the icon is associated with. This use is limited to a small subset of icons, including:

Code hierarchy palette

Folder

Visual Studio languages

Each of the common languages or platforms available in Visual Studio has an associated color. These colors are used on the base icon, or on language modifiers that appear in the upper right corner of compound icons.

Examples of icons with language modifiers

IntelliSense

IntelliSense icons use an exclusive color palette. These colors are used to help users quickly distinguish between the different items in the IntelliSense popup list.

Examples of IntelliSense icons

Notifications

Microsoft For Mac Image Library

Notifications in Visual Studio are used to indicate status. The notification palette uses the following four colors, as well as black or white foreground fill options, to define notifications with the following status levels.

Download Microsoft Office For Mac

Examples of notification icons

Microsoft Images Free