Fixed smart quotes (dotnet#2147)

Author: svick

Diff for: LICENSE

@@ -378,7 +378,7 @@ Section 8 -- Interpretation.
 Creative Commons is not a party to its public
 licenses. Notwithstanding, Creative Commons may elect to apply one of
 its public licenses to material it publishes and in those instances
-will be considered the “Licensor.” The text of the Creative Commons
+will be considered the "Licensor." The text of the Creative Commons
 public licenses is dedicated to the public domain under the CC0 Public
 Domain Dedication. Except for the limited purpose of indicating that
 material is shared under a Creative Commons public license or as

Diff for: xml/Microsoft.Build.Evaluation/ProjectCollection.xml

@@ -273,7 +273,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the MSBuild versions that were delivered with .Net 4.5 and Visual Studio 12.0, you must call UnloadProject() before the ProjectCollection goes out of scope.”  
+ In the MSBuild versions that were delivered with .Net 4.5 and Visual Studio 12.0, you must call UnloadProject() before the ProjectCollection goes out of scope."  
   
  ]]></format>
         </remarks>

Diff for: xml/Microsoft.Build.Evaluation/Toolset.xml

@@ -128,7 +128,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] is installed, use the base toolset and return a sub toolset version of “10.0”.  
+ If [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] is installed, use the base toolset and return a sub toolset version of "10.0".  
   
  Otherwise, use the highest-versioned sub toolset found. Sub toolsets with numbered versions are ordered numerically; any additional sub toolsets are prepended to the beginning of the list in the order found. Returns null if there is no sub toolset available and [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] is not installed.  
   
@@ -156,7 +156,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If “VisualStudioVersion” is set as a property on the toolset itself, then sub toolset version is set to “VisualStudioVersion”.  
+ If "VisualStudioVersion" is set as a property on the toolset itself, then sub toolset version is set to "VisualStudioVersion".  
   
  Otherwise, sub toolset version is set to the DefaultSubToolsetVersion of the toolset.  
   
@@ -189,9 +189,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the “VisualStudioVersion” global property exists in the set of global properties passed in, then sub toolset version is set to “VisualStudioVersion”.  
+ If the "VisualStudioVersion" global property exists in the set of global properties passed in, then sub toolset version is set to "VisualStudioVersion".  
   
- Otherwise, if “VisualStudioVersion” is set as a property on the toolset itself, then sub toolset version is set to “VisualStudioVersion”.  
+ Otherwise, if "VisualStudioVersion" is set as a property on the toolset itself, then sub toolset version is set to "VisualStudioVersion".  
   
  Otherwise, if the Visual Studio version corresponding to the solution version (Visual Studio version = solution version – 1) passed in maps to an existing sub toolset, then sub toolset version is set to the Visual Studio version.  
   

Diff for: xml/Microsoft.Build.Tasks.Windows/FileClassifier.xml

@@ -182,7 +182,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the output type of the assembly.</summary>
-        <value>The output type of the assembly.  Can be “exe” or “dll”.</value>
+        <value>The output type of the assembly.  Can be "exe" or "dll".</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>

Diff for: xml/Microsoft.Build.Tasks/Csc.xml

@@ -469,13 +469,13 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The name of the language passed to the “/preferreduilang” compiler option.</summary>
+        <summary>The name of the language passed to the "/preferreduilang" compiler option.</summary>
         <value>Returns the name of the language.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If set to null, “/preferreduilang” is omitted and the compiler uses its default setting.  
+ If set to null, "/preferreduilang" is omitted and the compiler uses its default setting.  
   
  ]]></format>
         </remarks>

Diff for: xml/Microsoft.Build.Tasks/GenerateBootstrapper.xml

@@ -441,7 +441,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The Visual Studio version, in the form &lt;major build.minor build&gt;, for example “4.0”.</summary>
+        <summary>The Visual Studio version, in the form &lt;major build.minor build&gt;, for example "4.0".</summary>
         <value>Returns <see cref="T:System.String" />.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />

Diff for: xml/Microsoft.Build.Tasks/GetInstalledSDKLocations.xml

@@ -13,7 +13,7 @@
   <Docs>
     <summary>Gathers the list of installed SDKS in the registry and on disk and outputs them into the project so they can be used during SDK reference resolution and RAR for single files.  
 
- GetInstalledSDKLocations doesn't recognize a version folder if “v” appears in its name.  For example, an SDK that's located at C:\Windows\Program Files\Microsoft SDKs\Windows\8.0\SDKFolders\3rdPartySDK\2.5\will be located correctly. However, the same SDK located atC:\Windows\Program Files\Microsoft SDKs\Windows\8.0\SDKFolders\3rdPartySDK\v2.5\won't be located and will be ignored. If an SDK is ignored, the failure won't be recorded in the log, and no error will be thrown.  
+ GetInstalledSDKLocations doesn't recognize a version folder if "v" appears in its name.  For example, an SDK that's located at C:\Windows\Program Files\Microsoft SDKs\Windows\8.0\SDKFolders\3rdPartySDK\2.5\will be located correctly. However, the same SDK located atC:\Windows\Program Files\Microsoft SDKs\Windows\8.0\SDKFolders\3rdPartySDK\v2.5\won't be located and will be ignored. If an SDK is ignored, the failure won't be recorded in the log, and no error will be thrown.  
 
  Version folder names need to be formed as major.minor[.build[.revision]]. For more information, see <see cref="M:System.Version.TryParse(System.String,System.Version@)" />.  
 

Diff for: xml/Microsoft.Build.Tasks/ResolveAssemblyReference.xml

@@ -1135,8 +1135,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a string value specifying the behavior when a mismatch between the target processor architecture and the architecture of a primary reference. When this is “Error”, an error will be logged for a mismatch. When this is “Warning”, a warning will be logged for a mismatch. When this is “None”, no error or warning will be logged for a mismatch.</summary>
-        <value>Returns a string value of “Error”, “Warning” or “None”.</value>
+        <summary>Gets or sets a string value specifying the behavior when a mismatch between the target processor architecture and the architecture of a primary reference. When this is "Error", an error will be logged for a mismatch. When this is "Warning", a warning will be logged for a mismatch. When this is "None", no error or warning will be logged for a mismatch.</summary>
+        <value>Returns a string value of "Error", "Warning" or "None".</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>

Diff for: xml/Microsoft.Build.Tasks/ResolveProjectBase.xml

@@ -49,7 +49,7 @@
       </Parameters>
       <Docs>
         <param name="currentProjectAbsolutePath">The absolute path of the current project.</param>
-        <summary>Helper method for retrieving the extra “project references” passed in the solution blob. These come from dependencies expressed in the solution file itself.</summary>
+        <summary>Helper method for retrieving the extra "project references" passed in the solution blob. These come from dependencies expressed in the solution file itself.</summary>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>

Diff for: xml/Microsoft.Build.Utilities/ToolLocationHelper.xml

@@ -1132,7 +1132,7 @@
       </Parameters>
       <Docs>
         <param name="sdkRoot">The root folder for the SDK, must contain a design-time folder.</param>
-        <param name="targetConfiguration">The configuration the SDK is targeting. This is “Debug” or “Retail”.</param>
+        <param name="targetConfiguration">The configuration the SDK is targeting. This is "Debug" or "Retail".</param>
         <param name="targetArchitecture">The architecture the SDK is targeting.</param>
         <summary>Get the list of SDK folders which contain the design-time files for the SDK at the specified SDK root. The list is in the order that must be used in searching for references.</summary>
         <returns>Returns the list of folders to be used in searching for design-time files in the SDK, in the order that must be used for the search.</returns>
@@ -1180,7 +1180,7 @@
       </Parameters>
       <Docs>
         <param name="sdkRoot">The root folder for the SDK, must contain a redist folder.</param>
-        <param name="targetConfiguration">The configuration the SDK is targeting. This is “Debug” or “Retail”.</param>
+        <param name="targetConfiguration">The configuration the SDK is targeting. This is "Debug" or "Retail".</param>
         <param name="targetArchitecture">The architecture the SDK is targeting.</param>
         <summary>Get the list of SDK folders which contain the redist files for the SDK at the specified SDK root. The list is in the order that must be used in searching for references.</summary>
         <returns>Returns the list of folders to be used in searching for redist files in the SDK, in the order that must be used for the search.</returns>
@@ -1228,7 +1228,7 @@
       </Parameters>
       <Docs>
         <param name="sdkRoot">The root folder for the SDK.</param>
-        <param name="targetConfiguration">The configuration the SDK is targeting. This is “Debug” or “Retail”.</param>
+        <param name="targetConfiguration">The configuration the SDK is targeting. This is "Debug" or "Retail".</param>
         <param name="targetArchitecture">The architecture the SDK is targeting.</param>
         <summary>Get the list of SDK folders which contain the references for the SDK at the specified SDK root. The list is in the order that must be used in searching for references.</summary>
         <returns>Returns the list of folders to be used in searching for references in the SDK, in the order that must be used for the search.</returns>

Diff for: xml/Microsoft.Win32.SafeHandles/CriticalHandleMinusOneIsInvalid.xml

@@ -32,7 +32,7 @@
 ## Remarks  
  This class derives from the <xref:System.Runtime.InteropServices.CriticalHandle?displayProperty=fullName> class. It describes the format of an invalid handle that uses a value of -1. Further derivations of this class (for example, file or registry handles) can specialize this further.  
   
- This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the <xref:System.IDisposable> interface topic.  
+ This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
 > [!NOTE]
 >  See the <xref:System.Runtime.InteropServices.CriticalHandle> class for important information on critical handle security and thread safety.  

Diff for: xml/Microsoft.Win32.SafeHandles/CriticalHandleZeroOrMinusOneIsInvalid.xml

@@ -34,7 +34,7 @@
   
  Use the <xref:Microsoft.Win32.SafeHandles.CriticalHandleZeroOrMinusOneIsInvalid> class when you need to wrap an unmanaged resource that does not have an existing managed wrapper.  
   
- This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the <xref:System.IDisposable> interface topic.  
+ This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
 > [!NOTE]
 >  See the <xref:System.Runtime.InteropServices.CriticalHandle> class for important information on critical handle security and thread safety.  

Diff for: xml/Microsoft.Win32.SafeHandles/SafeFileHandle.xml

@@ -38,7 +38,7 @@
  This class is derived from <xref:Microsoft.Win32.SafeHandles.SafeHandleZeroOrMinusOneIsInvalid>. A value of 0 or -1 is an invalid file handle.  
   
 > [!IMPORTANT]
->  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the <xref:System.IDisposable> interface topic.  
+>  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
    
   

Diff for: xml/Microsoft.Win32.SafeHandles/SafeHandleMinusOneIsInvalid.xml

@@ -33,7 +33,7 @@
  This class derives from the <xref:System.Runtime.InteropServices.SafeHandle?displayProperty=fullName> class. It describes the format of an invalid handle that uses a value of -1. Further derivations of this class (for example, file or registry handles) can specialize this further. See the <xref:Microsoft.Win32.SafeHandles.SafeFileHandle> class for an example of a class that derives from <xref:Microsoft.Win32.SafeHandles.SafeHandleMinusOneIsInvalid>.  
   
 > [!WARNING]
->  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`-`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the <xref:System.IDisposable> interface topic.  
+>  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`-`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
  ]]></format>
     </remarks>

Diff for: xml/Microsoft.Win32.SafeHandles/SafeHandleZeroOrMinusOneIsInvalid.xml

@@ -33,7 +33,7 @@
  This class derives from the <xref:System.Runtime.InteropServices.SafeHandle?displayProperty=fullName> class. It describes the format of an invalid handle. For example, some handles use -1 as an invalid handle value, while others use 0. Further derivations of this class (for example, file or registry handles) can specialize this further. See the <xref:Microsoft.Win32.SafeHandles.SafeFileHandle> class for an example of a class that derives from <xref:Microsoft.Win32.SafeHandles.SafeHandleZeroOrMinusOneIsInvalid>.  
   
 > [!IMPORTANT]
->  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the <xref:System.IDisposable> interface topic.  
+>  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
  Use the <xref:Microsoft.Win32.SafeHandles.SafeHandleZeroOrMinusOneIsInvalid> class whenever you need to safely wrap an unmanaged resource that does not have an existing managed wrapper.  
   

Diff for: xml/Microsoft.Win32.SafeHandles/SafeMemoryMappedFileHandle.xml

@@ -30,7 +30,7 @@
  Use the <xref:System.IO.MemoryMappedFiles.MemoryMappedFile.SafeMemoryMappedFileHandle%2A?displayProperty=fullName> property to obtain the safe handle.  
   
 > [!IMPORTANT]
->  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the <xref:System.IDisposable> interface topic.  
+>  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
  ]]></format>
     </remarks>

Diff for: xml/Microsoft.Win32.SafeHandles/SafeMemoryMappedViewHandle.xml

@@ -29,7 +29,7 @@
  Use the <xref:System.IO.MemoryMappedFiles.MemoryMappedViewAccessor.SafeMemoryMappedViewHandle%2A?displayProperty=fullName> property to obtain the safe handle.  
   
 > [!IMPORTANT]
->  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the <xref:System.IDisposable> interface topic.  
+>  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
  ]]></format>
     </remarks>