add monikers

Author: v-thepet

docs/ide/media/code-snippets-vb-property.png

@@ -19,11 +19,19 @@ You can distribute the compiler-generated XML file along with your .NET assembly
 
 ## Enable documentation generation
 
+   ::: moniker range=">= vs-2022"
 To enable documentation generation, select the **Generate a file containing API documentation** checkbox on the **Build** > **Output** tab of your project's properties.
 
 By default, a documentation file named the same as your assembly with an *.xml* file extension generates in the same directory as the assembly. If you want to configure a nondefault name or location for the  file, enter or browse to an alternate location under **XML documentation file path**.
+   ::: moniker-end
 
-Alternatively, you can add the [GenerateDocumentationFile](/dotnet/core/project-sdk/msbuild-props#generatedocumentationfile) or [DocumentationFile](/dotnet/core/project-sdk/msbuild-props#documentationfile) properties to your *.csproj*, *.vbproj*, or *.fsproj* file. Set `GenerateDocumentationFile` to `true` to generate a documentation file with the default name and location. Add the `DocumentationFile` property to specify a different name or location.
+   ::: moniker range="<= vs-2019"
+To enable documentation generation, select the **XML documentation file** checkbox in the **Build** > **Output** section of your project's properties.
+
+By default, a documentation file named the same as your assembly with an *.xml* file extension generates in the same directory as the assembly. If you want to configure a nondefault name or location for the  file, enter or browse to an alternate location.
+   ::: moniker-end
+
+Alternatively, you can add the [GenerateDocumentationFile](/dotnet/core/project-sdk/msbuild-props#generatedocumentationfile) or [DocumentationFile](/dotnet/core/project-sdk/msbuild-props#documentationfile) properties to your *.csproj*, *.vbproj*, or *.fsproj* file. Set `GenerateDocumentationFile` to `true` to generate a documentation file with the default name and location. Use the `DocumentationFile` property to specify a different name or location.
 
 If you use `DocumentationFile` by itself or with the `GenerateDocumentationFile` property set to `true`, a documentation file with the specified name and location is generated. However, if you set `GenerateDocumentationFile` to `false`, no documentation file is generated even if you set the `DocumentationFile` property.
 

docs/ide/reference/generate-xml-documentation-comments.md

@@ -90,12 +90,17 @@ You can create your own code snippets and add them to the code snippets that Vis
 
 1. In the **Import Code Snippet** dialog box, select the **My Code Snippets** folder in the right pane. Select **Finish**, and then select **OK**.
 
-1. The snippet is copied to one of the following locations, depending on the code language and version of Visual Studio that you're using:
+   The snippet is copied to one of the following locations, depending on the code language:
 
-   - *%USERPROFILE%\Documents\Visual Studio 2022\Code Snippets\Visual C#\My Code Snippets*
-   - *%USERPROFILE%\Documents\Visual Studio 2022\Code Snippets\Visual Basic\My Code Snippets*
-   - *%USERPROFILE%\Documents\Visual Studio 2019\Code Snippets\Visual C#\My Code Snippets*
-   - *%USERPROFILE%\Documents\Visual Studio 2019\Code Snippets\Visual Basic\My Code Snippets*
+   ::: moniker range=">= vs-2022"
+   *%USERPROFILE%\Documents\Visual Studio 2022\Code Snippets\Visual C#\My Code Snippets*
+   *%USERPROFILE%\Documents\Visual Studio 2022\Code Snippets\Visual Basic\My Code Snippets*
+   ::: moniker-end
+
+   ::: moniker range="<= vs-2019"
+   *%USERPROFILE%\Documents\Visual Studio 2019\Code Snippets\Visual C#\My Code Snippets*
+   *%USERPROFILE%\Documents\Visual Studio 2019\Code Snippets\Visual Basic\My Code Snippets*
+   ::: moniker-end
 
 1. Test your snippet by opening a C# or Visual Basic project. With a code file open in the editor, take one of the following actions:
 
@@ -109,12 +114,17 @@ You can create your own code snippets and add them to the code snippets that Vis
 
 The description field provides more information about your code snippet when viewed in the **Code Snippets Manager**. The shortcut is a tag you can type to insert your snippet.
 
-1. To edit your snippet, open the snippet file from the following location, depending on the code language and version of Visual Studio that you're using:
+1. To edit your snippet, open the snippet file from one of the following locations, depending on the code language:
 
+   ::: moniker range=">= vs-2022"
    - *%USERPROFILE%\Documents\Visual Studio 2022\Code Snippets\Visual C#\My Code Snippets/SquareRoot.snippet*
    - *%USERPROFILE%\Documents\Visual Studio 2022\Code Snippets\Visual Basic\My Code Snippets/SquareRoot.snippet*
+   ::: moniker-end
+
+   ::: moniker range="<= vs-2019"
    - *%USERPROFILE%\Documents\Visual Studio 2019\Code Snippets\Visual C#\My Code Snippets/SquareRoot.snippet*
    - *%USERPROFILE%\Documents\Visual Studio 2019\Code Snippets\Visual Basic\My Code Snippets/SquareRoot.snippet*
+   ::: moniker-end
 
    > [!TIP]
    > Because you're editing the file in the directory where Visual Studio placed it, you don't need to reimport it to Visual Studio.