Merge pull request #4938 from dotnet/master

Update Live with current Master

Author: mairaw

docs/csharp/language-reference/keywords/codesnippet/CSharp/stackalloc_1.cs

@@ -1,6 +1,6 @@
 ---
 title: "stackalloc (C# Reference)"
-ms.date: 07/20/2015
+ms.date: 04/12/2018
 ms.prod: .net
 ms.technology: 
   - "devlang-csharp"
@@ -10,45 +10,59 @@ f1_keywords:
   - "stackalloc"
 helpviewer_keywords: 
   - "stackalloc keyword [C#]"
-ms.assetid: adc04c28-3ed2-4326-807a-7545df92b852
-caps.latest.revision: 27
 author: "BillWagner"
 ms.author: "wiwagn"
 ---
 # stackalloc (C# Reference)
-The `stackalloc` keyword is used in an unsafe code context to allocate a block of memory on the stack.  
-  
-```csharp  
-int* block = stackalloc int[100];  
-```  
-  
-## Remarks  
- The keyword is valid only in local variable initializers. The following code causes compiler errors.  
-  
-```csharp  
-int* block;  
-// The following assignment statement causes compiler errors. You  
-// can use stackalloc only when declaring and initializing a local   
-// variable.  
-block = stackalloc int[100];  
-```  
-  
- Because pointer types are involved, `stackalloc` requires [unsafe](../../../csharp/language-reference/keywords/unsafe.md) context. For more information, see [Unsafe Code and Pointers](../../../csharp/programming-guide/unsafe-code-pointers/index.md).  
-  
- `stackalloc` is like [_alloca](/cpp/c-runtime-library/reference/alloca) in the C run-time library.  
-  
- The following example calculates and displays the first 20 numbers in the Fibonacci sequence. Each number is the sum of the previous two numbers. In the code, a block of memory of sufficient size to contain 20 elements of type `int` is allocated on the stack, not the heap. The address of the block is stored in the pointer `fib`. This memory is not subject to garbage collection and therefore does not have to be pinned (by using [fixed](../../../csharp/language-reference/keywords/fixed-statement.md)). The lifetime of the memory block is limited to the lifetime of the method that defines it. You cannot free the memory before the method returns.  
-  
-## Example  
- [!code-csharp[csrefKeywordsOperator#15](../../../csharp/language-reference/keywords/codesnippet/CSharp/stackalloc_1.cs)]  
-  
-## Security  
- Unsafe code is less secure than safe alternatives. However, the use of `stackalloc` automatically enables buffer overrun detection features in the common language runtime (CLR). If a buffer overrun is detected, the process is terminated as quickly as possible to minimize the chance that malicious code is executed.  
-  
-## C# Language Specification  
- [!INCLUDE[CSharplangspec](~/includes/csharplangspec-md.md)]  
-  
-## See Also  
+The `stackalloc` keyword is used in an unsafe code context to allocate a block of memory on the stack.
+
+```csharp
+int* block = stackalloc int[100];
+```
+
+## Remarks
+
+The keyword is valid only in local variable initializers. The following code causes compiler errors.
+
+```csharp
+int* block;
+// The following assignment statement causes compiler errors. You
+// can use stackalloc only when declaring and initializing a local
+// variable.
+block = stackalloc int[100];
+```
+
+Beginning with C# 7.3, you can use array initializer syntax for `stackalloc` arrays. All the following declarations declare an array with three elements whose values are the integers `1`, `2`, and `3`:
+
+```csharp
+// Valid starting with C# 7.3
+int* first = stackalloc int[3] { 1, 2, 3 };
+int* second = stackalloc int[] { 1, 2, 3 };
+int* third = stackalloc[] { 1, 2, 3 };
+```
+
+Because pointer types are involved, `stackalloc` requires an [unsafe](unsafe.md) context. For more information, see [Unsafe Code and Pointers](../../programming-guide/unsafe-code-pointers/index.md) 
+
+`stackalloc` is like [_alloca](/cpp/c-runtime-library/reference/alloca) in the C run-time library.
+
+## Examples
+
+The following example calculates and displays the first 20 numbers in the Fibonacci sequence. Each number is the sum of the previous two numbers. In the code, a block of memory of sufficient size to contain 20 elements of type `int` is allocated on the stack, not the heap. The address of the block is stored in the pointer `fib`. This memory is not subject to garbage collection and therefore does not have to be pinned (by using [fixed](fixed-statement.md)). The lifetime of the memory block is limited to the lifetime of the method that defines it. You cannot free the memory before the method returns.
+
+[!code-csharp[csrefKeywordsOperator#15](../../../../samples/snippets/csharp/keywords/StackAllocExamples.cs#1)]
+
+The following example initializes a `stackalloc` array of integers to a bit mask with one bit set in each element. This demonstrates the new initializer syntax available starting in C# 7.3:
+
+[!code-csharp[csrefKeywordsOperator#15](../../../../samples/snippets/csharp/keywords/StackAllocExamples.cs#2)]
+
+## Security
+
+Unsafe code is less secure than safe alternatives. However, the use of `stackalloc` automatically enables buffer overrun detection features in the common language runtime (CLR). If a buffer overrun is detected, the process is terminated as quickly as possible to minimize the chance that malicious code is executed.
+
+## C# Language Specification
+ [!INCLUDE[CSharplangspec](~/includes/csharplangspec-md.md)]
+
+## See Also
  [C# Reference](../../../csharp/language-reference/index.md)  
  [C# Programming Guide](../../../csharp/programming-guide/index.md)  
  [C# Keywords](../../../csharp/language-reference/keywords/index.md)  

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

@@ -74,7 +74,7 @@ foreach (string element in elements)
  On each subsequent iteration of the `foreach` loop, the execution of the iterator body continues from where it left off, again stopping when it reaches a `yield return` statement. The `foreach` loop completes when the end of the iterator method or a `yield break` statement is reached.  
 
 ## Example  
- The following example has a `yield return` statement that's inside a `for` loop. Each iteration of the `foreach` statement body in `Process` creates a call to the `Power` iterator function. Each call to the iterator function proceeds to the next execution of the `yield return` statement, which occurs during the next iteration of the `for` loop.  
+ The following example has a `yield return` statement that's inside a `for` loop. Each iteration of the `foreach` statement body in the `Main` method creates a call to the `Power` iterator function. Each call to the iterator function proceeds to the next execution of the `yield return` statement, which occurs during the next iteration of the `for` loop.  
 
  The return type of the iterator method is <xref:System.Collections.IEnumerable>, which is an iterator interface type. When the iterator method is called, it returns an enumerable object that contains the powers of a number.  
 

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

@@ -1,7 +1,7 @@
 ---
 title: ".NET Framework Deployment Guide for Administrators"
 ms.custom: ""
-ms.date: "03/30/2017"
+ms.date: "04/10/2018"
 ms.prod: ".net-framework"
 ms.reviewer: ""
 ms.suite: ""
@@ -160,7 +160,7 @@ This step-by-step article describes how a system administrator can deploy the [!
 
 8.  Complete the wizard.  
 
- The packagenow contains all the information you need to silently deploy the .NET Framework 4.5. Before you deploy the package and program, verify that it was installed on the distribution point; see the "Monitor Content" section of [Operations and Maintenance for Content Management in Configuration Manager](http://technet.microsoft.com/library/gg712694.aspx#BKMK_MonitorContent) in the Configuration Manager Documentation Library.  
+ The package now contains all the information you need to silently deploy the .NET Framework 4.5. Before you deploy the package and program, verify that it was installed on the distribution point; see the "Monitor Content" section of [Operations and Maintenance for Content Management in Configuration Manager](http://technet.microsoft.com/library/gg712694.aspx#BKMK_MonitorContent) in the Configuration Manager Documentation Library.  
 
 <a name="deploying_package"></a>   
 ### Deploy the package  
@@ -225,12 +225,16 @@ This step-by-step article describes how a system administrator can deploy the [!
 ## Troubleshooting  
 
 ### Log file locations  
- The following log files are generated during [!INCLUDE[net_v45](../../../includes/net-v45-md.md)] setup:  
+ The following log files are generated during .NET Framework setup:  
 
- %temp%\Microsoft .NET Framework 4.5*.txt  
- %temp%\Microsoft .NET Framework 4.5*.html  
+ %temp%\Microsoft .NET Framework *version*\*.txt  
+ %temp%\Microsoft .NET Framework *version*\*.html  
 
- You can use the [log collection tool](http://www.microsoft.com/download/details.aspx?id=12493) to collect the [!INCLUDE[net_v45](../../../includes/net-v45-md.md)] log files and to create a compressed cabinet (.cab) file that reduces the size of the files.  
+ where *version* is the version of the .NET Framework that you're installing, such as 4.5 or 4.7.2.  
+ 
+ You can also specify the directory to which log files are written by using the `/log` command-line option in the .NET Framework installation command. For more information, see [.NET Framework deployment guide for developers](deployment-guide-for-developers.md#command-line-options). 
+ 
+ You can use the [log collection tool](https://www.microsoft.com/download/details.aspx?id=12493) to collect the .NET Framework log files and to create a compressed cabinet (.cab) file that reduces the size of the files.  
 
 <a name="return_codes"></a>   
 ### Return codes