Merge branch 'master' into tglee-vsinstall

Author: TerryGLee

mac/TOC.md

@@ -12,7 +12,6 @@
 
 # [Customizing the IDE](customizing-the-ide.md)
 ## [Extending Visual Studio for Mac](extending-visual-studio-mac.md)
-### [Extending Visual Studio for Mac Walkthrough](extending-visual-studio-mac-walkthrough.md)
 
 
 # [Projects and Solutions](projects-and-solutions.md)
@@ -55,5 +54,7 @@
 ### [Setup](setup-vsmac-tools-unity.md)
 ### [Using Unity Tools](using-vsmac-tools-unity.md)
 
+# [Accessibility](accessibility.md)
+
 # [Troubleshooting](troubleshooting.md)
 ## [Report a Problem](report-a-problem.md)

mac/accessibility.md

@@ -0,0 +1,74 @@
+---
+title: "Accessibility"
+description: 
+author: asb3993
+ms.author: amburns
+ms.date: 08/15/2017
+ms.topic: article
+ms.assetid: 2C4AAC2E-3B4A-4496-8BE0-1F5A7F81D1CA
+---
+
+# Accessibility
+
+In addition to features and utilities in macOS, Visual Studio for Mac has the following features, making it more accessible for people with disabilities:
+
+- Text Enlargement in the Solution and Editor Pads
+- Text size options in the editors
+- Color customization in the editors
+- Keyboard shortcut customization
+- Code-completion for methods and parameters 
+
+For more information on accessibility features in macOS, see [Apple's website](https://www.apple.com/accessibility/mac/).
+
+## Using Accessibility features in Visual Studio for Mac
+
+The Accessibility features in Visual Studio for Mac are turned off by default. To enable them, do the following steps:
+
+1. Go to **Visual Studio > Preferences > Other > Accessibility**.
+
+2. Select the **Enable Accessibility** checkbox, as illustrated in the following diagram:
+
+    ![Enable accessibility checkbox](media/accessibility-image1.png)
+
+3. Press the **Restart Visual Studio** button to allow the accessibility features to take effect.
+
+
+Alternatively, you can use the command line to enable accessibility features. To do this, enter the following command in terminal: 
+
+```bash
+defaults write com.microsoft.visual-studio com.monodevelop.AccessibilityEnabled 1 
+```
+
+After turning on accessibility, you need to restart Visual Studio.
+
+## How to: Use Keyboard Navigation
+
+Keyboard navigation can be enabled by setting the Full Keyboard Access option in **System Preferences > Keyboard > Shortcuts** to **All Controls**:
+
+  ![Systems preferences panel in macos](media/accessibility-image2.png)
+
+Setting full keyboard access turns on the focus rectangle. You can then select controls using:
+- Tab to go forward through controls
+- Shift-Tab to go backwards through controls
+- Arrow keys to move between controls in the direction of the arrows. 
+
+Pressing the Space bar activates the focused control.
+
+## How to: Enable and use Voice Over
+
+Turn VoiceOver on or off press **Cmd + F5**
+
+To navigate through the UI VoiceOver commands, use the following commands:
+
+- Move VoiceOver cursor between Controls: **Ctrl + Alt + Left arrow key / Right arrow key**
+
+VoiceOver reads out the name of the controls, some details about it, and what you can do with it. 
+
+- Enter Groups and controls (such as the Solution Pad, Toolbox, and other Pads): **Ctrl + Alt + Shift + Down Arrow**
+
+Once inside a control, you can use **Ctrl + Alt + Arrows** to move around inside it. 
+ 
+For general information on using VoiceOver in macOS, refer to the following guides:
+
+- [Getting Started with VoiceOver](https://help.apple.com/voiceover/info/guide/10.12/)
+- [VoiceOver commands in macOS](http://lab.dotjay.com/notes/voiceover-commands/)

mac/benefits-vsmac-over-xs.md

@@ -144,17 +144,17 @@ While Xamarin cross-platform features have always been a first-class feature of
 
 ### Android 
 
-* [Android SDK manager](https://developer.xamarin.com/guides/android/application_fundamentals/using-the-sdk-manager/) (**Preview**) 
+* [Android SDK manager](https://developer.xamarin.com/guides/android/application_fundamentals/using-the-sdk-manager/)  
 * Android O will only be supported in Visual Studio for Mac, not 
 Xamarin Studio 
 
 ### iOS and Mac 
 
 * [iOS signing workflow updates ](https://developer.xamarin.com/guides/cross-platform/macios/apple-account-management/) 
     * Create signing identities and install them to the local Keychain. 
-    * Create Provisioning Profiles. (**Preview**)
-    * Add a signing identity to an existing profile. (**Preview**)
-    *  Provision devices: register a device in the Apple Developer Portal and add them to a provisioning profile. (**Preview**)
+    * Create Provisioning Profiles. 
+    * Add a signing identity to an existing profile.
+    *  Provision devices: register a device in the Apple Developer Portal and add them to a provisioning profile.
 * iOS 11, watchOS 4, and tvOS 2 will only be supported in Visual Studio for Mac, not Xamarin Studio 
 * MacOS High Sierra will only be supported in Visual Studio for Mac, not Xamarin Studio 
 

mac/extending-visual-studio-mac.md

@@ -26,7 +26,7 @@ The benefit of this modular design is that Visual Studio for Mac is extensible -
 > [!NOTE]
 > **Note**: If you have an Add-in Maker project that was created before Add-in Maker 1.2, you need to migrate your project as outlined in the steps [here](https://mhut.ch/addinmaker/1.2).
 
-The [Walkthrough](~/extending-visual-studio-mac-walkthrough.md) topic explains how to build an extension package that uses a *Command* to insert the date and time into an open text document.
+<!---The [Walkthrough](~/extending-visual-studio-mac-walkthrough.md) topic explains how to build an extension package that uses a *Command* to insert the date and time into an open text document.--->
 
 This section looks at the different files generated by the Add-in Maker and the data a command extension requires.
 
@@ -54,11 +54,17 @@ They also have their corresponding `assembly:AddinDependency ` attributes added
 
 An extension point is a placeholder that defines a data structure (a type), while an extension defines data that conforms to a structure specified by a specific extension point. Extension points specify what type of extension they can accept in their declaration. Extensions are declared using type names or extension paths. See the [Extension Point reference](http://monoaddins.codeplex.com/wikipage?title=Extension%20Points&referringTitle=Description%20of%20Add-ins%20and%20Add-in%20Roots) for a more in-depth explanation on how to create the extension point that you need.
 
-The extension/extension point architecture keeps the development of Visual Studio for Mac fast and modular. Since there are a large number of extension types, this article focuses on the ones used in the extension package that was built in the [Walkthrough](~/extending-visual-studio-mac-walkthrough.md).
+The extension/extension point architecture keeps the development of Visual Studio for Mac fast and modular. 
+
+<!--Since there are a large number of extension types, this article focuses on the ones used in the extension package that was built in the [Walkthrough](~/extending-visual-studio-mac-walkthrough.md).-->
 
 ### Command Extensions
 
-[Walkthrough](~/extending-visual-studio-mac-walkthrough.md) uses a Command Extension - an extension that points to methods that are called every time it is executed. Command Extensions are defined by adding entries to the `/MonoDevelop/Ide/Commands` extension point. We defined our extension in `Manifest.addin.xml` with the following code:
+<!--[Walkthrough](~/extending-visual-studio-mac-walkthrough.md) uses a Command Extension - an extension that points to methods that are called every time it is executed. -->
+
+Command Extensions are extensions that point to methods that are called every time it is executed.
+
+Command Extensions are defined by adding entries to the `/MonoDevelop/Ide/Commands` extension point. We defined our extension in `Manifest.addin.xml` with the following code:
 
  ```
 <Extension path="/MonoDevelop/Ide/Commands/Edit">
@@ -76,7 +82,9 @@ The extension node contains a path attribute that specifies the extension point
 *   **_description** - The text to be shown as a tooltip for toolbar buttons.
 *   **defaultHandler** - Specifies the `CommandHandler` class that powers the Command
 
-To invoke the command from the Edit Menu, the walkthrough creates a CommandItem extension that plugs into the `/MonoDevelop/Ide/MainMenu/Edit` extension point:
+<!--To invoke the command from the Edit Menu, the walkthrough creates a CommandItem extension that plugs into the `/MonoDevelop/Ide/MainMenu/Edit` extension point:-->
+
+A CommandItem extension that plugs into the `/MonoDevelop/Ide/MainMenu/Edit` extension point is demonstrated in the following code snippet:
 
 ```
 <Extension path="/MonoDevelop/Ide/MainMenu/Edit">
@@ -121,7 +129,9 @@ This ties together the Command and CommandItem - the CommandItem calls the Comma
 
 ## IDE APIs
 
-The extension package detailed in the [Walkthrough](~/extending-visual-studio-mac-walkthrough.md) deals with the Text Editor in Visual Studio for Mac, but this is only one of many possible areas for customization. For information on the scope of areas that are available for development, see the [Extension Tree Reference](http://monodevelop.com/Developers/Articles/Extension_Tree_Reference) and the [API Overview](http://monodevelop.com/Developers/Articles/API_Overview). When building advanced extension packages, also refer to [Developer Articles](http://monodevelop.com/Developers/Articles). Below is a partial list of areas for customization:
+<!--The extension package detailed in the [Walkthrough](~/extending-visual-studio-mac-walkthrough.md) deals with the Text Editor in Visual Studio for Mac, but this is only one of many possible areas for customization. -->
+
+For information on the scope of areas that are available for development, see the [Extension Tree Reference](http://monodevelop.com/Developers/Articles/Extension_Tree_Reference) and the [API Overview](http://monodevelop.com/Developers/Articles/API_Overview). When building advanced extension packages, also refer to [Developer Articles](http://monodevelop.com/Developers/Articles). Below is a partial list of areas for customization:
 
 *   Pads
 *   Key Binding Schemes
@@ -148,4 +158,4 @@ The extension package detailed in the [Walkthrough](~/extending-visual-studio-ma
 ## Additional Information
 
 > [!NOTE]
-We are currently working on improving the extensibility scenarios for Visual Studio for Mac. If you are creating extensions and need additional help or information, or would like to provide feedback, please contact [email protected]
+We are currently working on improving the extensibility scenarios for Visual Studio for Mac. If you are creating extensions and need additional help or information, or would like to provide feedback, please fill in the [Visual Studio for Mac Extension Authoring](https://aka.ms/vsmac-extensions-survey) form.

mac/index.md

@@ -18,7 +18,7 @@ Visual Studio for Mac is a modern, sophisticated IDE with many features for crea
 * ASP.NET Core Web applications
 * Cross-platform Unity games
 
-It includes a rich editor, debugging, native platform integration with iOS, Mac and Android, and integrated source control to name just of few of its many features.
+It includes a rich editor, debugging, native platform integration with iOS, Mac and Android, and integrated source control to name just a few of its many features.
 
 This topic surveys various sections of Visual Studio for Mac, providing a look at some of the features that make it a powerful tool for creating cross-platform applications.