Merge pull request #5965 from dotnet/master

Update live with current master

Author: mairaw

docs/core/tools/dotnet-new.md

@@ -3,7 +3,7 @@ title: dotnet new command - .NET Core CLI
 description: The dotnet new command creates new .NET Core projects based on the specified template.
 author: mairaw
 ms.author: mairaw
-ms.date: 05/29/2018
+ms.date: 06/12/2018
 ---
 # dotnet new
 
@@ -145,8 +145,8 @@ Lists templates containing the specified name. If invoked for the `dotnet new` c
 
 The language of the template to create. The language accepted varies by the template (see defaults in the [arguments](#arguments) section). Not valid for some templates.
 
-    > [!NOTE]
-    > Some shells interpret `#` as a special character. In those cases, you need to enclose the language parameter value, such as `dotnet new console -lang "F#"`.
+> [!NOTE]
+> Some shells interpret `#` as a special character. In those cases, you need to enclose the language parameter value, such as `dotnet new console -lang "F#"`.
 
 `-n|--name <OUTPUT_NAME>`
 
@@ -196,8 +196,8 @@ Lists templates containing the specified name. If invoked for the `dotnet new` c
 
 The language of the template to create. The language accepted varies by the template (see defaults in the [arguments](#arguments) section). Not valid for some templates.
 
-    > [!NOTE]
-    > Some shells interpret `#` as a special character. In those cases, you need to enclose the language parameter value, such as `dotnet new console -lang "F#"`.
+> [!NOTE]
+> Some shells interpret `#` as a special character. In those cases, you need to enclose the language parameter value, such as `dotnet new console -lang "F#"`.
 
 `-n|--name <OUTPUT_NAME>`
 
@@ -237,8 +237,8 @@ Lists templates containing the specified name. If invoked for the `dotnet new` c
 
 The language of the template to create. The language accepted varies by the template (see defaults in the [arguments](#arguments) section). Not valid for some templates.
 
-    > [!NOTE]
-    > Some shells interpret `#` as a special character. In those cases, you need to enclose the language parameter value, such as `dotnet new console -lang "F#"`.
+> [!NOTE]
+> Some shells interpret `#` as a special character. In those cases, you need to enclose the language parameter value, such as `dotnet new console -lang "F#"`.
 
 `-n|--name <OUTPUT_NAME>`
 
@@ -496,13 +496,13 @@ Create a .NET Standard class library project in the specified directory (availab
 
 `dotnet new classlib -lang VB -o MyLibrary`
 
-Create a new ASP.NET Core C# MVC application project in the current directory with no authentication targeting .NET Core 2.0:
+Create a new ASP.NET Core C# MVC application project in the current directory with no authentication:
 
-`dotnet new mvc -au None -f netcoreapp2.0`
+`dotnet new mvc -au None`
 
-Create a new xUnit application targeting .NET Core 2.0:
+Create a new xUnit application:
 
-`dotnet new xunit --framework netcoreapp2.0`
+`dotnet new xunit`
 
 List all templates available for MVC:
 
@@ -521,4 +521,4 @@ Create a *global.json* in the current directory setting the SDK version to 2.0.0
 [Custom templates for dotnet new](custom-templates.md)  
 [Create a custom template for dotnet new](~/docs/core/tutorials/create-custom-template.md)  
 [dotnet/dotnet-template-samples GitHub repo](https://github.com/dotnet/dotnet-template-samples)  
-[Available templates for dotnet new](https://github.com/dotnet/templating/wiki/Available-templates-for-dotnet-new)
+[Available templates for dotnet new](https://github.com/dotnet/templating/wiki/Available-templates-for-dotnet-new)

docs/core/tools/dotnet-sln.md

@@ -3,7 +3,7 @@ title: dotnet sln command - .NET Core CLI
 description: The dotnet-sln command provides a convenient option to add, remove, and list projects in a solution file.
 author: mairaw
 ms.author: mairaw
-ms.date: 05/29/2018
+ms.date: 06/13/2018
 ---
 # dotnet sln
 
@@ -28,6 +28,12 @@ dotnet sln [-h|--help]
 
 The `dotnet sln` command provides a convenient way to add, remove, and list projects in a solution file.
 
+To use the `dotnet sln` command, the solution file must already exist. If you need to create one, use the [dotnet new](dotnet-new.md) command, like in the following example:
+
+```
+dotnet new sln
+```
+
 ## Commands
 
 `add <PROJECT> ...`

docs/csharp/language-reference/configure-language-version.md

@@ -88,7 +88,7 @@ You can create a **Directory.build.props** file that contains the `<LangVersion>
 </Project>
 ```
 
-Now, builds in every subdirectory of the directory containing that file will use C# version 7.3 syntax. For more information, see the article on [Customize your build](/visualstudio/msbuild/customize-your-build.md).
+Now, builds in every subdirectory of the directory containing that file will use C# version 7.3 syntax. For more information, see the article on [Customize your build](/visualstudio/msbuild/customize-your-build).
 
 ## Set the langversion compiler option
 

docs/csharp/language-reference/keywords/accessibility-domain.md

@@ -13,7 +13,7 @@ The accessibility domain of a member specifies in which program sections a membe
 ## Example  
  This example contains a top-level type, `T1`, and two nested classes, `M1` and `M2`. The classes contain fields that have different declared accessibilities. In the `Main` method, a comment follows each statement to indicate the accessibility domain of each member. Notice that the statements that try to reference the inaccessible members are commented out. If you want to see the compiler errors caused by referencing an inaccessible member, remove the comments one at a time.  
 
- [!code-csharp[csrefKeywordsModifiers#4](../../../csharp/language-reference/keywords/codesnippet/CSharp/accessibility-domain_1.cs)]  
+[!code-csharp[csrefKeywordsModifiers#4](~/samples/snippets/csharp/VS_Snippets_VBCSharp/csrefKeywordsModifiers/CS/csrefKeywordsModifiers.cs#4)]
 
 ## C# Language Specification  
  [!INCLUDE[CSharplangspec](~/includes/csharplangspec-md.md)]  

docs/csharp/language-reference/keywords/add.md

@@ -13,7 +13,7 @@ The `add` contextual keyword is used to define a custom event accessor that is i
 ## Example  
  The following example shows an event that has custom `add` and [remove](../../../csharp/language-reference/keywords/remove.md) accessors. For the full example, see [How to:  Implement Interface Events](../../../csharp/programming-guide/events/how-to-implement-interface-events.md).  
 
- [!code-csharp[csrefKeywordsContextual#15](../../../csharp/language-reference/keywords/codesnippet/CSharp/add_1.cs)]  
+[!code-csharp[csrefKeywordsContextual#15](~/samples/snippets/csharp/VS_Snippets_VBCSharp/csrefKeywordsContextual/CS/csrefKeywordsContextual.cs#15)]
 
  You do not typically need to provide your own custom event accessors. The accessors that are automatically generated by the compiler when you declare an event are sufficient for most scenarios.  
 

docs/csharp/language-reference/keywords/as.md

@@ -12,7 +12,7 @@ ms.assetid: a9be126b-cbf4-4990-a70d-d0e1983cad0e
 # as (C# Reference)
 You can use the `as` operator to perform certain types of conversions between compatible reference types or [nullable types](../../../csharp/programming-guide/nullable-types/index.md). The following code shows an example.  
 
- [!code-csharp[csrefKeywordsOperator#1](../../../csharp/language-reference/keywords/codesnippet/CSharp/as_1.cs)]  
+[!code-csharp[csrefKeywordsOperator#1](~/samples/snippets/csharp/VS_Snippets_VBCSharp/csrefKeywordsOperator/CS/csrefKeywordsOperators.cs#1)]
 
 ## Remarks  
  The `as` operator is like a cast operation. However, if the conversion isn't possible, `as` returns `null` instead of raising an exception. Consider the following example:  
@@ -30,7 +30,8 @@ expression is type ? (type)expression : (type)null
  Note that the `as` operator performs only reference conversions, nullable conversions, and boxing conversions. The `as` operator can't perform other conversions, such as user-defined conversions, which should instead be performed by using cast expressions.  
 
 ## Example  
- [!code-csharp[csrefKeywordsOperator#2](../../../csharp/language-reference/keywords/codesnippet/CSharp/as_2.cs)]  
+
+[!code-csharp[csrefKeywordsOperator#2](~/samples/snippets/csharp/VS_Snippets_VBCSharp/csrefKeywordsOperator/CS/csrefKeywordsOperators.cs#2)]
 
 ## C# Language Specification  
  [!INCLUDE[CSharplangspec](~/includes/csharplangspec-md.md)]  

docs/csharp/language-reference/keywords/ascending.md

@@ -14,7 +14,7 @@ The `ascending` contextual keyword is used in the [orderby clause](../../../csha
 ## Example  
  The following example shows the use of `ascending` in an [orderby clause](../../../csharp/language-reference/keywords/orderby-clause.md).  
 
- [!code-csharp[csrefKeywordsContextual#14](../../../csharp/language-reference/keywords/codesnippet/CSharp/ascending_1.cs)]  
+[!code-csharp[csrefKeywordsContextual#14](~/samples/snippets/csharp/VS_Snippets_VBCSharp/csrefKeywordsContextual/CS/csrefKeywordsContextual.cs#14)]
 
 ## See Also  
  [C# Reference](../../../csharp/language-reference/index.md)