Merge pull request #794 from MicrosoftDocs/gewarren-bugfixes

Fixed bugs/github issues

Author: gewarren

docs/ide/create-portable-custom-editor-options.md

@@ -6,32 +6,13 @@ ms.reviewer: ""
 ms.suite: ""
 ms.tgt_pltfrm: ""
 ms.topic: "article"
-dev_langs: 
-  - "VB"
-  - "CSharp"
-  - "C++"
-  - "aspx"
 helpviewer_keywords: 
   - "editor"
 ms.assetid: 
 caps.latest.revision: 29
 author: "gewarren"
 ms.author: "gewarren"
 manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
 ms.technology: 
   - "vs-ide-general"
 ---
@@ -88,13 +69,36 @@ Now, when you press the TAB key, you get Tab characters instead of spaces.
 
 In most cases when you implement a Visual Studio language service, no additional work is needed to support EditorConfig universal properties. The core editor automatically discovers and reads the .editorconfig file when users open files, and it sets the appropriate text buffer and view options. However, some language services opt to use an appropriate contextual text view option rather than using global settings for items such as tabs and spaces when a user edits or formats text. In these cases, the language service must be updated to support EditorConfig files.
 
-The following table lists the changes needed to update a language service to support EditorConfig files.
+Following are the changes needed to update a language service to support EditorConfig files, by replacing a global language-specific option with a contextual option:
 
-| Deprecated global language-specific option | Contextual option replacement |
-| :------------- | :------------- |
-| Microsoft.VisualStudio.TextManager.Interop.LANGPREFERENCES.fInsertTabs or Microsoft.VisualStudio.Package.LanguagePreferences.InsertTabs | !textBufferOptions.GetOptionValue(DefaultOptions.ConvertTabsToSpacesOptionId) or !textView.Options.GetOptionValue(DefaultOptions.ConvertTabsToSpacesOptionId) |
-| Microsoft.VisualStudio.TextManager.Interop.LANGPREFERENCES.uIndentSize or Microsoft.VisualStudio.Package.LanguagePreferences.InsertTabs.IndentSize | textBufferOptions.GetOptionValue(DefaultOptions. IndentSizeOptionId) or textView.Options.GetOptionValue(DefaultOptions. IndentSizeOptionId) |
-| Microsoft.VisualStudio.TextManager.Interop.LANGPREFERENCES.uTabSize or Microsoft.VisualStudio.Package.LanguagePreferences.InsertTabs.TabSize | textBufferOptions.GetOptionValue(DefaultOptions.TabSizeOptionId) or textView.Options.GetOptionValue(DefaultOptions.TabSizeOptionId) |
+Replace:  
+
+Microsoft.VisualStudio.TextManager.Interop.LANGPREFERENCES.fInsertTabs or Microsoft.VisualStudio.Package.LanguagePreferences.InsertTabs  
+
+With:  
+
+!textBufferOptions.GetOptionValue(DefaultOptions.ConvertTabsToSpacesOptionId) or
+!textView.Options.GetOptionValue(DefaultOptions.ConvertTabsToSpacesOptionId)  
+
+*****
+Replace:  
+
+Microsoft.VisualStudio.TextManager.Interop.LANGPREFERENCES.uIndentSize or Microsoft.VisualStudio.Package.LanguagePreferences.InsertTabs.IndentSize  
+
+With:  
+
+textBufferOptions.GetOptionValue(DefaultOptions. IndentSizeOptionId) or 
+textView.Options.GetOptionValue(DefaultOptions. IndentSizeOptionId)  
+
+*****
+Replace:  
+
+Microsoft.VisualStudio.TextManager.Interop.LANGPREFERENCES.uTabSize or Microsoft.VisualStudio.Package.LanguagePreferences.InsertTabs.TabSize  
+
+With:  
+
+textBufferOptions.GetOptionValue(DefaultOptions.TabSizeOptionId) or 
+textView.Options.GetOptionValue(DefaultOptions.TabSizeOptionId)  
 
 # See Also
 [Create Portable Custom Editor Options with EditorConfig](create-portable-custom-editor-options.md)

docs/ide/media/buildwalk_configurationmanagerdialogbox.png

@@ -1,5 +1,4 @@
 # [Visual Studio Reference](visual-studio-reference.md)
-# [Visual Studio for Applications Reference](visual-studio-for-applications-reference.md)
 # [General User Interface Elements](general-user-interface-elements-visual-studio.md)
 ## [Call Hierarchy](call-hierarchy.md)
 ## [Choose Toolbox Items, WPF Components](choose-toolbox-items-wpf-components.md)

docs/ide/media/buildwalk_csharpbuildoutputwnd.png

@@ -1,34 +1,5 @@
 ---
-title: "Visual Studio for Applications Reference | Microsoft Docs"
-ms.custom: ""
-ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "vs-ide-general"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-ms.assetid: 877a0fa3-4b6f-4056-b320-d8727793f708
-caps.latest.revision: 3
-author: "gewarren"
-ms.author: "gewarren"
-manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
+redirect_url: /visualstudio/ide/reference/visual-studio-reference
 ---
 # Visual Studio for Applications Reference
-The Visual Studio for Applications namespaces provide interfaces for integrating .NET Framework script engines into applications.  
-  
-## In This Section
+The Visual Studio for Applications namespaces provide interfaces for integrating .NET Framework script engines into applications.  

docs/ide/media/buildwalk_csharpsupresswarnings.png

@@ -45,9 +45,6 @@ This section includes user interface reference, language equivalents, and other
  [XML Tools in Visual Studio](../../xml-tools/xml-tools-in-visual-studio.md)  
  Contains documents about the XML tools in Visual Studio and provides links to more information.  
 
- [Visual Studio for Applications Reference](../../ide/reference/visual-studio-for-applications-reference.md)  
- Contains reference documentation for interfaces that you can use to integrate .NET Framework script engines into applications.  
-  
  [MSBuild](../../msbuild/msbuild.md)
  Contains documents about how to use the Microsoft build platform, which is integrated into [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)].  
 

docs/ide/media/buildwalk_extensionsdialogsampledownload.png

@@ -1,7 +1,7 @@
 ---
 title: "Walkthrough: Building an Application | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "09/25/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -13,23 +13,9 @@ caps.latest.revision: 8
 author: "gewarren"
 ms.author: "gewarren"
 manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
 ---
 # Walkthrough: Building an Application
-By completing this walkthrough, you'll  become more familiar with several options that you can configure when you build applications with Visual Studio. You'll create a custom build configuration, hide certain warning messages, and increase build output information, among other tasks, for a sample application.  
+By completing this walkthrough, you'll become more familiar with several options that you can configure when you build applications with Visual Studio. You'll create a custom build configuration, hide certain warning messages, and increase build output information for a sample application.  
 
  This topic contains the following sections:  
 
@@ -46,43 +32,7 @@ By completing this walkthrough, you'll  become more familiar with several option
  [Create a Release Build](../ide/walkthrough-building-an-application.md#BKMK_releasebuild)  
 
 ##  <a name="BKMK_installapp"></a> Install the Sample Application  
- You'll use the **Extensions and Updates** dialog box to find and install the [Introduction to Building WPF Applications](http://code.msdn.microsoft.com/Introduction-to-Building-b8d16419?SRC=VSIDE) sample from the Samples Gallery on the Microsoft website. The Samples Gallery provides a variety of example projects and code that you can download and review as you plan and develop your applications.  
-  
-#### To install the sample application  
-  
-1.  On the menu bar, choose **Tools**, **Extensions and Updates**.  
-  
-2.  Choose the **Online** category, and then choose the **Samples Gallery** category.  
-  
-3.  Specify `Introduction` in the search box to find the sample.  
-  
-     ![Extensions and Updates dialog box](../ide/media/buildwalk_extensionsdialogsampledownload.png "BuildWalk_ExtensionsDialogSampleDownload")  
-  
-4.  In the results list, choose either **Introduction to Building WPF Applications (Visual C#)** or **Introduction to Building WPF Applications (Visual Basic)**.  
-  
-5.  Choose the **Download** button, and then choose the **Close** button.  
-  
- The Introduction to Building WPF Applications sample appears in the **New Project** dialog box.  
-  
-#### To create a solution for the sample application  
-  
-1.  Open the **New Project** dialog box.  
-  
-     ![On the menu bar, choose File, New, Project](../ide/media/exploreide-filenewproject.png "ExploreIDE-FileNewProject")  
-  
-2.  In the **Installed** category, choose the **Samples** category to display the Introduction to Building WPF Applications sample.  
-  
-3.  Name the solution `IntroWPFcsharp` for Visual C#.  
-  
-     ![New Project dialog box, Installed Samples](../ide/media/buildwalk_newprojectdlgintrotowpfsample.png "BuildWalk_NewProjectdlgIntrotoWPFsample")  
-  
-     OR  
-  
-     Name the solution `IntroWPFvb` for Visual Basic.  
-  
-     ![New Project dialog box, Visual Basic Sample](../ide/media/buildwalk_newprojectdlgintrotowpfsamplevb.png "BuildWalk_NewProjectdlgIntrotoWPFsampleVB")  
-  
-4.  Choose the **OK** button.  
+Download the [Introduction to Building WPF Applications](https://code.msdn.microsoft.com/Introduction-to-Building-b8d16419) sample. Choose either C# or Visual Basic. After the .zip file has downloaded, extract it and open the **ExpenseItIntro.sln** file using Visual Studio.  
 
 ##  <a name="BKMK_CreateBuildConfig"></a> Create a Custom Build Configuration  
  When you create a solution, debug and release build configurations and their default platform targets are defined for the solution automatically. You can then customize these configurations or create your own. Build configurations specify the build type. Build platforms specify the operating system that an application targets for that configuration. For more information, see [Understanding Build Configurations](../ide/understanding-build-configurations.md), [Understanding Build Platforms](../ide/understanding-build-platforms.md), and [Debug and Release Project Configurations](http://msdn.microsoft.com/en-us/0440b300-0614-4511-901a-105b771b236e).  
@@ -95,15 +45,15 @@ By completing this walkthrough, you'll  become more familiar with several option
 
      ![Build menu, Configuration Manager command](../ide/media/buildwalk_configurationmanagerdialogbox.png "BuildWalk_ConfigurationManagerDialogBox")  
 
-2.  In the **Active solution configuration** list, choose **New**.  
+2.  In the **Active solution configuration** list, choose **\<New...\>**.  
 
 3.  In the **New Solution Configuration** dialog box, name the new configuration `Test`, copy settings from the existing Debug configuration, and then choose the **OK** button.  
 
      ![New Solution Configuration Dialog Box](../ide/media/buildwalk_newsolutionconfigdlgbox.png "BuildWalk_NewSolutionConfigDlgBox")  
 
-4.  In the **Active solution platform** list, choose **New**.  
+4.  In the **Active solution platform** list, choose **\<New...\>**.  
 
-5.  In the **New Solution Platform** dialog box, choose**x64**, and don't copy settings from the x86 platform.  
+5.  In the **New Solution Platform** dialog box, choose **x64**, and don't copy settings from the x86 platform.  
 
      ![New Solution Platform Dialog Box](../ide/media/buildwalk_newsolutionplatform.png "BuildWalk_NewSolutionPlatform")  
 
@@ -113,9 +63,11 @@ By completing this walkthrough, you'll  become more familiar with several option
 
  ![Configuration Manager with Test configuration](../ide/media/buildwalk_configmanagertestconfig.png "BuildWalk_ConfigManagerTestconfig")  
 
- You can quickly verify or change the active solution configuration by using the **Solution Configurations** list on the **Standard** toolbar.  
+7. Choose **Close**.  
+
+You can quickly verify or change the active solution configuration by using the **Solution Configurations** list on the **Standard** toolbar.  
 
- ![Solution Configuration option Standard Toolbar](../ide/media/buildwalk_standardtoolbarsolutioncongfig.png "BuildWalk_StandardToolbarSolutionCongfig")  
+![Solution Configuration option Standard Toolbar](../ide/media/buildwalk_standardtoolbarsolutioncongfig.png "BuildWalk_StandardToolbarSolutionCongfig")  
 
 ##  <a name="BKMK_building"></a> Build the Application  
  Next, you'll build the solution with the custom build configuration.  
@@ -124,8 +76,21 @@ By completing this walkthrough, you'll  become more familiar with several option
 
 -   On the menu bar, choose **Build**, **Build Solution**.  
 
- The **Output** window displays the results of the build. The build succeeded, but several warning messages were generated.  
+    The **Output** window displays the results of the build. The build succeeded.  
 
+##  <a name="BKMK_hidewarning"></a> Hide Compiler Warnings  
+Next we'll introduce some code that causes a warning to be generated by the compiler.  
+
+1. In the C# project, open the **ExpenseReportPage.xaml.cs** file. In the **ExpenseReportPage** method, add the following code: `int i;`.  
+
+    OR
+
+    In the Visual Basic project, open the **ExpenseReportPage.xaml.vb** file. In the custom constructor **Public Sub New...**, add the following code: `Dim i`.  
+
+2. Build the solution.  
+
+The **Output** window displays the results of the build. The build succeeded, but warnings were generated:  
+
  Figure 1: Visual Basic warnings  
 
  ![Output Window Visual Basic](../ide/media/buildwalk_vbbuildoutputwnd.png "BuildWalk_VBBuildOutputWnd")  
@@ -134,9 +99,8 @@ By completing this walkthrough, you'll  become more familiar with several option
 
  ![Output Window Visual C&#35;](../ide/media/buildwalk_csharpbuildoutputwnd.png "BuildWalk_CsharpBuildOutputWnd")  
 
-##  <a name="BKMK_hidewarning"></a> Hide Compiler Warnings  
- You can temporarily hide certain warning messages during a build rather than have them clutter up the build output.  
-  
+You can temporarily hide certain warning messages during a build rather than have them clutter up the build output.  
+
 #### To hide a specific Visual C# warning  
 
 1.  In **Solution Explorer**, choose the top-level project node.  
@@ -145,7 +109,7 @@ By completing this walkthrough, you'll  become more familiar with several option
 
      The **Project Designer** opens.  
 
-3.  Choose the **Build** page and then, in the **Suppress warnings** box, specify the warning number `1762`.  
+3.  Choose the **Build** page and then, in the **Suppress warnings** box, specify the warning number **0168**.  
 
      ![Build page, Project Designer](../ide/media/buildwalk_csharpsupresswarnings.png "BuildWalk_CsharpSupressWarnings")  
 
@@ -199,7 +163,7 @@ By completing this walkthrough, you'll  become more familiar with several option
 
 5.  Build the solution, and then review the information in the **Output** window.  
 
-     The build information includes the time that the build started (located at the beginning), the order in which files were processed, and the amount of time that the process took to complete (located at the end). This information also includes the actual compiler syntax that Visual Studio runs during the build.  
+     The build information includes the time that the build started (located at the beginning) and the order in which files were processed. This information also includes the actual compiler syntax that Visual Studio runs during the build.  
 
      For example, in the Visual C# build, the [/nowarn](/dotnet/visual-basic/reference/command-line-compiler/nowarn) option lists the warning code, 1762, that you specified earlier in this topic, along with three other warnings.  
 
@@ -208,7 +172,7 @@ By completing this walkthrough, you'll  become more familiar with several option
     > [!TIP]
     >  You can search the contents of the **Output** window if you display the **Find** dialog box by choosing the Ctrl+F keys.  
   
- For more information, see [How to: View, Save, and Configure Build Log Files](../ide/how-to-view-save-and-configure-build-log-files.md).  
+For more information, see [How to: View, Save, and Configure Build Log Files](../ide/how-to-view-save-and-configure-build-log-files.md).  
 
 ##  <a name="BKMK_releasebuild"></a> Create a Release Build  
  You can build a version of the sample application that's optimized for shipping it. For the release build, you'll specify that the executable is copied to a network share before the build is kicked off.  
@@ -257,13 +221,15 @@ By completing this walkthrough, you'll  become more familiar with several option
     > [!IMPORTANT]
     >  A message box might appear, warning you that the network share that you've specified might not be a trusted location. If you trust the location that you've specified, choose the **OK** button in the message box.  
   
-6.  Build the application.  
+6.  On the **Standard toolbar**, set the Solution Configurations to **Release** and the Solution Platforms to **x86**.  
+
+7.  Build the application.  
 
      ![Build Solution command on the Build menu](../ide/media/exploreide-buildsolution.png "ExploreIDE-BuildSolution")  
 
  The executable file is copied to the network path that you specified. Its path would be \\\myserver\builds\\*FileName*.exe.  
 
- Congratulations: you've successfully completed this walkthrough.  
+Congratulations: you've successfully completed this walkthrough.  
 
 ## See Also  
  [Walkthrough: Building a Project (C++)](/cpp/ide/walkthrough-building-a-project-cpp)