Merge pull request #6046 from dotnet/master

mairaw · web-flow · commit 3d42e1d73e21 · 2018-06-20T00:23:11.000-07:00
Update live with current master
diff --git a/docs/csharp/quick-starts/branches-and-loops.yml b/docs/csharp/quick-starts/branches-and-loops.yml
@@ -268,6 +268,7 @@ items:
     > [!NOTE]
     > This online coding experience is in preview mode. If you encounter problems, please report them [on the dotnet/try repo](https://github.com/dotnet/try/issues).
 
+- title: Congratulations!
   content: |
     You've completed the "branches and loops" quickstart. 
     
diff --git a/docs/csharp/roslyn-sdk/get-started/semantic-analysis.md b/docs/csharp/roslyn-sdk/get-started/semantic-analysis.md
@@ -126,7 +126,7 @@ Select only the name property, and only distinct names by removing any overloads
 
 You can also build the full query using the LINQ query syntax, and then display all the method names in  the console:
 
-[!code-csharp[build and display the results of this query.](../../../../samples/csharp/roslyn-sdk/SemanticQuickStart/Program.cs#12 "Build and display the results of the query.")]
+[!code-csharp[build and display the results of this query.](../../../../samples/csharp/roslyn-sdk/SemanticQuickStart/Program.cs#13 "Build and display the results of the query.")]
 
 Build and run the program. You should see the following output:
 
diff --git a/docs/framework/app-domains/assembly-security-considerations.md b/docs/framework/app-domains/assembly-security-considerations.md
@@ -39,9 +39,13 @@ ms.author: "ronpet"
  At load time, the assembly's evidence is used as input to security policy. Security policy is established by the enterprise and the computer's administrator as well as by user policy settings, and determines the set of permissions that is granted to all managed code when executed. Security policy can be established for the publisher of the assembly (if it has a signing tool generated signature), for the Web site and zone (in Internet Explorer terms) the assembly was downloaded from, or for the assembly's strong name. For example, a computer's administrator can establish security policy that allows all code downloaded from a Web site and signed by a given software company to access a database on a computer, but does not grant access to write to the computer's disk.  
   
 ## Strong-Named Assemblies and Signing Tools  
+
+ > [!WARNING]
+ > Do not rely on strong names for security. They provide a unique identity only.
+
  You can sign an assembly in two different but complementary ways: with a strong name or by using  [SignTool.exe (Sign Tool)](../../../docs/framework/tools/signtool-exe.md). Signing an assembly with a strong name adds public key encryption to the file containing the assembly manifest. Strong name signing helps to verify name uniqueness, prevent name spoofing, and provide callers with some identity when a reference is resolved.  
   
- However, no level of trust is associated with a strong name, which makes [SignTool.exe (Sign Tool)](../../../docs/framework/tools/signtool-exe.md) important. The two signing tools require a publisher to prove its identity to a third-party authority and obtain a certificate. This certificate is then embedded in your file and can be used by an administrator to decide whether to trust the code's authenticity.  
+ No level of trust is associated with a strong name, which makes [SignTool.exe (Sign Tool)](../../../docs/framework/tools/signtool-exe.md) important. The two signing tools require a publisher to prove its identity to a third-party authority and obtain a certificate. This certificate is then embedded in your file and can be used by an administrator to decide whether to trust the code's authenticity.  
   
  You can give both a strong name and a digital signature created using [SignTool.exe (Sign Tool)](../../../docs/framework/tools/signtool-exe.md) to an assembly, or you can use either alone. The two signing tools can sign only one file at a time; for a multifile assembly, you sign the file that contains the assembly manifest. A strong name is stored in the file containing the assembly manifest, but a signature created using [SignTool.exe (Sign Tool)](../../../docs/framework/tools/signtool-exe.md) is stored in a reserved slot in the portable executable (PE) file containing the assembly manifest. Signing of an assembly using [SignTool.exe (Sign Tool)](../../../docs/framework/tools/signtool-exe.md) can be used (with or without a strong name) when you already have a trust hierarchy that relies on[SignTool.exe (Sign Tool)](../../../docs/framework/tools/signtool-exe.md) generated signatures, or when your policy uses only the key portion and does not check a chain of trust.  
   
diff --git a/docs/framework/app-domains/create-and-use-strong-named-assemblies.md b/docs/framework/app-domains/create-and-use-strong-named-assemblies.md
@@ -17,6 +17,9 @@ ms.author: "ronpet"
 ---
 # Creating and Using Strong-Named Assemblies
 <a name="top"></a> A strong name consists of the assembly's identity—its simple text name, version number, and culture information (if provided)—plus a public key and a digital signature. It is generated from an assembly file using the corresponding private key. (The assembly file contains the assembly manifest, which contains the names and hashes of all the files that make up the assembly.)  
+
+> [!WARNING]
+> Do not rely on strong names for security. They provide a unique identity only.
   
  A strong-named assembly can only use types from other strong-named assemblies. Otherwise, the integrity of the strong-named assembly would be compromised.  
   
diff --git a/docs/framework/install/on-windows-10.md b/docs/framework/install/on-windows-10.md
@@ -60,7 +60,7 @@ The .NET Framework 3.5 supports apps built for the .NET Framework 1.0 through 3.
 
 - You cannot install an earlier version of the .NET Framework on your machine if a later version is already installed.
 
-- 4.x versions of the .NET Framework can be used to run applications built for the .NET Framework 4.0 through that version. For example, .NET Framework 4.7 can be used to run applications built for the .NET Framework 4.0 through 4.7. The latest version (the .NET Framework 4.7.1) can be used to run applications built will all versions of the .NET Framework starting with 4.0.
+- 4.x versions of the .NET Framework can be used to run applications built for the .NET Framework 4.0 through that version. For example, .NET Framework 4.7 can be used to run applications built for the .NET Framework 4.0 through 4.7. The latest version (the .NET Framework 4.7.2) can be used to run applications built with all versions of the .NET Framework starting with 4.0.
 
 For a list of all the versions of the .NET Framework available to download, see the [.NET Downloads](https://www.microsoft.com/net/download?utm_source=ms-docs&utm_medium=referral) page.
 
diff --git a/docs/framework/tools/developer-command-prompt-for-vs.md b/docs/framework/tools/developer-command-prompt-for-vs.md
@@ -1,6 +1,6 @@
 ---
 title: "Developer Command Prompt for Visual Studio"
-ms.date: "03/30/2017"
+ms.date: "06/18/2018"
 helpviewer_keywords: 
   - "command prompt, Windows SDK"
   - "Visual Studio command prompt"
@@ -14,72 +14,75 @@ author: "mairaw"
 ms.author: "mairaw"
 ---
 # Developer Command Prompt for Visual Studio
-The Developer Command Prompt for Visual Studio automatically sets the environment variables that enable you to easily use .NET Framework tools. The Developer Command Prompt is installed with full or community editions of Visual Studio. It is not installed with the Express versions of Visual Studio.  
-  
-<a name="find"></a>   
-## Searching for the Command Prompt on your machine  
- You may see multiple command prompts, depending on the version of Visual Studio and any additional SDKs you've installed. For example, 64-bit versions of Visual Studio provide both 32-bit and 64-bit command prompts. (The 32-bit and 64-bit versions of most tools are identical; however, a few tools make changes specific to 32-bit and 64-bit environments.) If the steps below don't work, you can try [Manually locating the files on your machine](#alternative) or [Running command prompt from inside Visual Studio](#visualstudio).  
-  
- **In Windows 10**  
-  
-1.  Open the **Start** menu, by pressing the Windows logo key ![Windows logo](../../../docs/framework/get-started/media/windowskeyboardlogo.png "Windowskeyboardlogo") on your keyboard for example.  
-  
-2.  On the **Start** menu, enter `dev`. This will bring a list of installed apps that match your search pattern. If you're looking for a different command prompt, try entering a different search term such as `prompt`.  
-  
-3.  Choose the **Developer Command Prompt** (or the command prompt you want to use).  
-  
- **In Windows 8.1**  
-  
-1.  Go to the **Start** screen, by pressing the Windows logo key ![Windows logo](../../../docs/framework/get-started/media/windowskeyboardlogo.png "Windowskeyboardlogo") on your keyboard for example.  
-  
-2.  On the **Start** screen, press `CTRL + TAB` to open the **Apps** list and then enter `V`. This will bring a list that includes all installed Visual Studio command prompts.  
-  
-3.  Choose the **Developer Command Prompt** (or the command prompt you want to use).  
-  
- **In Windows 8**  
-  
-1.  Go to the **Start** screen, by pressing the Windows logo key ![Windows logo](../../../docs/framework/get-started/media/windowskeyboardlogo.png "Windowskeyboardlogo") on your keyboard for example.  
-  
-2.  On the **Start** screen, press the Windows logo key ![Windows logo](../../../docs/framework/get-started/media/windowskeyboardlogo.png "Windowskeyboardlogo") `+ Z`.  
-  
-3.  Choose the **Apps view** icon at the bottom of the screen and then enter `V`. This will bring a list that includes all installed Visual Studio command prompts.  
-  
-4.  Choose the **Developer Command Prompt** (or the command prompt you want to use).  
-  
- **In Windows 7**  
-  
-1.  Choose **Start**, expand **All Programs**, and then expand **Microsoft Visual Studio**.  
-  
-2.  Depending on the version of Visual Studio you have installed, choose  **Visual Studio Tools**, **Visual Studio Command Prompt**, or the command prompt you want to use.  
-  
- If you have the [Windows SDK](http://msdn.microsoft.com/windows/desktop/aa904949) or [Windows Phone SDK](https://dev.windowsphone.com/downloadsdk) installed, you may see additional command prompts for ARM, x86, or x64 architectures. Check the documentation for the individual tools to determine which version of the command prompt you should use.  
-  
-<a name="alternative"></a>   
-## Manually locating the files on your machine  
-  Usually, the shortcuts for the command prompts you have installed will be placed at the **Start Menu** folder for Visual Studio, such as in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 2015\Visual Studio Tools.    But if for some reason, searching for the command prompt doesn't yield the expected results, you can try to manually locate the shortcut on your machine in order to use it.   Try searching for the name of the command prompt file such as VsDevCmd.bat or go to the Tools folder such as C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools (path will change according to your Visual Studio version and installation location).  
-  
-<a name="visualstudio"></a>   
-## Running command prompt from inside Visual Studio  
- For easier access, you can add the Visual Studio Developer Command Prompt  or any other command prompt to the Tools menu on Visual Studio, by adding it to the external tools list. This is how you can accomplish that:  
-  
-1.  Open Visual Studio.  
-  
-2.  Select the **Tools** menu and choose **External Tools...**.  
-  
-3.  On the **External Tools** dialog box, choose the **Add** button. A new entry appears  
-  
-4.  Enter a **Title** for your new menu item such as `Command Prompt`.  
-  
-5.  In the **Command** field, specify the file you want to launch such as `%comspec%` or `C:\Windows\System32\cmd.exe` .  
-  
-6.  In the **Arguments** field, specify where to find the specific command prompt you want to use such as `/k "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\VsDevCmd.bat"` (this will launch the Developer Command Prompt installed with [!INCLUDE[vs_dev14](../../../includes/vs-dev14-md.md)]). This value needs to be changed according to your Visual Studio version and installation location.  
-  
-7.  Choose a value for the **Initial directory** field such as **Project Directory** .  
-  
-8.  Choose the **OK** button.  
-  
- After that, the new menu item is added and you can access the command prompt from the **Tools** menu.  
-  
-## See Also  
+
+The Developer Command Prompt for Visual Studio automatically sets the environment variables that enable you to easily use .NET Framework tools. The Developer Command Prompt is installed with full or community editions of Visual Studio. It isn't installed with the Express versions of Visual Studio.
+
+> [!div class="button"]
+[Download Visual Studio](https://www.visualstudio.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017)
+
+## Searching for the Command Prompt on your machine
+
+You may see many command prompts, depending on the version of Visual Studio and any additional SDKs you've installed. For example, 64-bit versions of Visual Studio provide both 32-bit and 64-bit command prompts. (The 32-bit and 64-bit versions of most tools are the same; however, a few tools make changes specific to 32-bit and 64-bit environments.) If the following steps don't work, you can try [Manually locating the files on your machine](#manually-locating-the-files-on-your-machine) or [Running command prompt from inside Visual Studio](#running-command-prompt-from-inside-visual-studio).
+
+### In Windows 10
+
+1. In the search box on the taskbar, start typing the name of the tool, such as `dev` or `developer command prompt`. This brings a list of installed apps that match your search pattern. If you're looking for a different command prompt, try entering a different search term such as `prompt`.
+
+2. Choose the **Developer Command Prompt** (or the command prompt you want to use).
+
+### In Windows 8.1
+
+1. Go to the **Start** screen, by pressing the Windows logo key ![Windows logo](../get-started/media/windowskeyboardlogo.png "Windowskeyboardlogo") on your keyboard for example.
+
+2. On the **Start** screen, press `CTRL + TAB` to open the **Apps** list and then enter `V`. This brings a list that includes all installed Visual Studio command prompts.
+
+3. Choose the **Developer Command Prompt** (or the command prompt you want to use).
+
+### In Windows 8
+
+1. Go to the **Start** screen, by pressing the Windows logo key ![Windows logo](../get-started/media/windowskeyboardlogo.png "Windowskeyboardlogo") on your keyboard for example.
+
+2. On the **Start** screen, press the Windows logo key ![Windows logo](../get-started/media/windowskeyboardlogo.png "Windowskeyboardlogo") `+ Z`.
+
+3. Choose the **Apps view** icon at the bottom of the screen and then enter `V`. This brings a list that includes all installed Visual Studio command prompts.
+
+4. Choose the **Developer Command Prompt** (or the command prompt you want to use).
+
+### In Windows 7
+
+1. Choose **Start**, expand **All Programs**, and then expand **Microsoft Visual Studio**.
+
+2. Depending on the version of Visual Studio you've installed, choose  **Visual Studio Tools**, **Visual Studio Command Prompt**, or the command prompt you want to use.
+
+If you have other SDKs installed such as the [Windows 10 SDK](https://developer.microsoft.com/windows/downloads/windows-10-sdk) or [previous versions](https://developer.microsoft.com/windows/downloads/sdk-archive) installed, you may see additional command prompts for ARM, x86, or x64 architectures. Check the documentation for the individual tools to determine which version of the command prompt you should use.
+
+## Manually locating the files on your machine
+
+Usually, the shortcuts for the command prompts you have installed are placed at the **Start Menu** folder for Visual Studio, such as in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 2017\Visual Studio Tools. But if for some reason, searching for the command prompt doesn't bring the expected results, you can try to manually locate the shortcut on your machine. Try searching for the name of the command prompt file, such as *VsDevCmd.bat*, or go to the Tools folder such as C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools (path changes according to your Visual Studio version, edition, and installation location).
+
+## Running command prompt from inside Visual Studio
+
+For easier access, you can add the Visual Studio Developer Command Prompt  or any other command prompt to the Tools menu on Visual Studio, by adding it to the external tools list. This is how you can accomplish that:
+
+1. Open Visual Studio.
+
+2. Select the **Tools** menu and choose **External Tools**.
+
+3. On the **External Tools** dialog box, choose the **Add** button. A new entry appears.
+
+4. Enter a **Title** for your new menu item such as `Command Prompt`.
+
+5. In the **Command** field, specify the file you want to launch such as `%comspec%` or `C:\Windows\System32\cmd.exe`.
+
+6. In the **Arguments** field, specify where to find the specific command prompt you want to use such as `/k "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\VsDevCmd.bat"` (this command launches the Developer Command Prompt that is installed with Visual Studio 2017 Enterprise). Change this value according to your Visual Studio version, edition, and installation location.
+
+7. Choose a value for the **Initial directory** field such as **Project Directory**.
+
+8. Choose the **OK** button.
+
+After that, the new menu item is added and you can access the command prompt from the **Tools** menu.
+
+## See also
+
  [Tools](../../../docs/framework/tools/index.md)  
- [Managing External Tools](/visualstudio/ide/managing-external-tools)
+ [Managing External Tools](/visualstudio/ide/managing-external-tools)  
diff --git a/docs/framework/tools/sn-exe-strong-name-tool.md b/docs/framework/tools/sn-exe-strong-name-tool.md
@@ -16,6 +16,9 @@ ms.author: "ronpet"
 # Sn.exe (Strong Name Tool)
 The Strong Name tool (Sn.exe) helps sign assemblies with [strong names](../../../docs/framework/app-domains/strong-named-assemblies.md). Sn.exe provides options for key management, signature generation, and signature verification.  
   
+> [!WARNING]
+> Do not rely on strong names for security. They provide a unique identity only.
+
  For more information on strong naming and strong-named assemblies, see [Strong-Named Assemblies](../../../docs/framework/app-domains/strong-named-assemblies.md) and [How to: Sign an Assembly with a Strong Name](../../../docs/framework/app-domains/how-to-sign-an-assembly-with-a-strong-name.md).  
   
  The Strong Name tool is automatically installed with Visual Studio. To start the tool, use the Developer Command Prompt (or the Visual Studio Command Prompt in Windows 7). For more information, see [Command Prompts](../../../docs/framework/tools/developer-command-prompt-for-vs.md).  
diff --git a/docs/framework/winforms/advanced/how-to-copy-pixels-for-reducing-flicker-in-windows-forms.md b/docs/framework/winforms/advanced/how-to-copy-pixels-for-reducing-flicker-in-windows-forms.md
@@ -22,7 +22,7 @@ When you animate a simple graphic, users can sometimes encounter flicker or othe
  In the example below, a shape is drawn on the form in its <xref:System.Windows.Forms.Control.Paint> event handler. Then, the <xref:System.Drawing.Graphics.CopyFromScreen%2A> method is used to duplicate the shape.  
   
 > [!NOTE]
->  Setting the form's <xref:System.Windows.Forms.Control.DoubleBuffered%2A> property to `true` will make graphics-based code in the <xref:System.Windows.Forms.Control.Paint> event be double-buffered. While this will not have any discernable performance gains when using the code below, it is something to keep in mind when working with more complex graphics-manipulation code.  
+>  Setting the form's <xref:System.Windows.Forms.Control.DoubleBuffered%2A> property to `true` will make graphics-based code in the <xref:System.Windows.Forms.Control.Paint> event be double-buffered. While this will not have any discernible performance gains when using the code below, it is something to keep in mind when working with more complex graphics-manipulation code.  
   
 ## Example  
   
