Merge pull request #289186 from MicrosoftDocs/main

10/24/2024 PM Publish

Author: Taojunshen

articles/application-gateway/media/application-gateway-create-probe-portal/figure6.png

@@ -76,7 +76,7 @@ Vector similarity search can be used in multiple applications. Some common use-c
 - **Document Retrieval**. Use the deeper semantic understanding of text provided by LLMs to provide a richer document search experience where traditional keyword-based search falls short. [Document Retrieval Example](https://github.com/RedisVentures/redis-arXiv-search)
 - **Product Recommendation**. Find similar products or services to recommend based on past user activities, like search history or previous purchases. [Product Recommendation Example](https://github.com/RedisVentures/LLM-Recommender)
 - **Visual Search**. Search for products that look similar to a picture taken by a user or a picture of another product. [Visual Search Example](https://github.com/RedisVentures/redis-product-search)
-- **Semantic Caching**. Reduce the cost and latency of LLMs by caching LLM completions. LLM queries are compared using vector similarity. If a new query is similar enough to a previously cached query, the cached query is returned. [Semantic Caching example using LangChain](https://python.langchain.com/docs/integrations/llms/llm_caching#redis-cache)
+- **Semantic Caching**. Reduce the cost and latency of LLMs by caching LLM completions. LLM queries are compared using vector similarity. If a new query is similar enough to a previously cached query, the cached query is returned. [Semantic Caching example using LangChain](https://python.langchain.com/docs/integrations/llm_caching/#redis-cache)
 - **LLM Conversation Memory**. Persist conversation history with an LLM as embeddings in a vector database. Your application can use vector search to pull relevant history or "memories" into the response from the LLM. [LLM Conversation Memory example](https://github.com/continuum-llms/chatgpt-memory)
 
 ## Why choose Azure Cache for Redis for storing and searching vectors?

articles/azure-cache-for-redis/cache-overview-vector-similarity.md

@@ -10,61 +10,6 @@ ms.date: 03/20/2024
 
 This article describes how to resolve potential errors in your Bicep installation.
 
-## .NET runtime error
-
-When installing the Bicep extension for Visual Studio Code, you may run into the following error messages:
-
-```error
-Failed to install .NET runtime v5.0
-```
-
-```error
-Failed to download .NET 5.0.x ....... Error!
-```
-
-> [!WARNING]
-> This is a last resort solution that may cause problems when updating versions.
-
-To solve the problem, you can manually install .NET from the [.NET website](https://aka.ms/dotnet-core-download), and then configure Visual Studio Code to reuse an existing installation of .NET with the following settings:
-
-**Windows**
-
-```json
-"dotnetAcquisitionExtension.existingDotnetPath": [
-  {
-    "extensionId": "ms-azuretools.vscode-bicep",
-    "path": "C:\\Program Files\\dotnet\\dotnet.exe"
-  }
-]
-
-```
-
-**macOS**
-
-If you need an **x64** installation, use:
-
-```json
-"dotnetAcquisitionExtension.existingDotnetPath": [
-  {
-    "extensionId": "ms-azuretools.vscode-bicep",
-    "path": "/usr/local/share/dotnet/x64/dotnet"
-  }
-]
-```
-
-For other **macOS** installations, use:
-
-```json
-"dotnetAcquisitionExtension.existingDotnetPath": [
-  {
-    "extensionId": "ms-azuretools.vscode-bicep",
-    "path": "/usr/local/share/dotnet/dotnet"
-  }
-]
-```
-
-See [User and Workspace Settings](https://code.visualstudio.com/docs/getstarted/settings) for configuring Visual Studio Code settings.
-
 ## Visual Studio Code error
 
 If you see the following error message popup in Visual Studio Code:
@@ -77,7 +22,7 @@ From VS Code, open the **Output** view in the pane at the bottom of the screen,
 
   :::image type="content" source="./media/installation-troubleshoot/visual-studio-code-output-pane-bicep.png" alt-text="Visual Studio Code output pane":::
 
-If you see the following output in the pane, and you're using Bicep CLI **version 0.4.1124** or later, check whether you have added the `dotnetAcquisitionExtension.existingDotnetPath` configuration option to VS Code. See [.NET runtime error](#net-runtime-error). If this configuration option is present, remove it and restart VS Code.
+If you see the following output in the pane, check whether you have added the `dotnetAcquisitionExtension.existingDotnetPath` setting to VS Code. If this setting is present, remove it and restart VS Code. See [User and Workspace Settings](https://code.visualstudio.com/docs/getstarted/settings) for configuring Visual Studio Code settings.
 
   ```error
   It was not possible to find any compatible framework version.

articles/azure-resource-manager/bicep/installation-troubleshoot.md

@@ -2,7 +2,7 @@
 title: Create & deploy Visual Studio resource group projects
 description: Use Visual Studio to create an Azure resource group project and deploy the resources to Azure.
 ms.topic: how-to
-ms.date: 03/20/2024
+ms.date: 10/24/2024
 ---
 
 # Creating and deploying Azure resource groups through Visual Studio
@@ -11,7 +11,7 @@ ms.date: 03/20/2024
 > The Azure Resource Group project is now in extended support, meaning we will continue to support existing features and capabilities but won't prioritize adding new features.
 
 > [!NOTE]
-> For the best and most secure experience, we strongly recommend updating your Visual Studio installation to the [latest Long-Term Support (LTS) version](/visualstudio/install/update-visual-studio?view=vs-2022). Upgrading will improve both the reliability and overall performance of your Visual Studio environment.
+> For the best and most secure experience, we strongly recommend updating your Visual Studio installation to the [latest Long-Term Support (LTS) version](/visualstudio/install/update-visual-studio). Upgrading will improve both the reliability and overall performance of your Visual Studio environment. If you choose not to upgrade, you may encounter the issues documented in [Issues when creating and deploying Azure resource groups through Visual Studio](https://learn.microsoft.com/troubleshoot/developer/visualstudio/ide/troubleshoot-create-deploy-resource-group).
 
 With Visual Studio, you can create a project that deploys your infrastructure and code to Azure. For example, you can deploy the web host, website, and code for the website. Visual Studio provides many different starter templates for deploying common scenarios. In this article, you deploy a web app.
 
@@ -22,9 +22,9 @@ This article shows how to use [Visual Studio 2019 or later with the Azure develo
 In this section, you create an Azure Resource Group project with a **Web app** template.
 
 1. In Visual Studio, choose **File**>**New**>**Project**.
-1. Select the **Azure Resource Group** project template and **Next**.
+1. Search **resource group**, and then select the **Azure Resource Group (extended support)** project template and **Next**.
 
-    :::image type="content" source="./media/create-visual-studio-deployment-project/create-project.png" alt-text="Screenshot of Create a new project window highlighting Azure Resource Group and Next button.":::
+    :::image type="content" source="./media/create-visual-studio-deployment-project/add-app.png" alt-text="Screenshot of Create a new project window highlighting Azure Resource Group and Next button.":::
 
 1. Give your project a name. The other default settings are probably fine, but review them to make they work for your environment. When done, select **Create**.
 
@@ -64,7 +64,7 @@ You can customize a deployment project by modifying the Resource Manager templat
 
    :::image type="content" source="./media/create-visual-studio-deployment-project/navigate-json.png" alt-text="Screenshot of the Visual Studio editor with a selected element in the JSON Outline window.":::
 
-1. You can add a resource by either selecting the **Add Resource** button at the top of the JSON Outline window, or by right-clicking **resources** and selecting **Add New Resource**.
+1. You can add a resource by right-clicking **resources** and selecting **Add New Resource**.
 
    :::image type="content" source="./media/create-visual-studio-deployment-project/add-resource.png" alt-text="Screenshot of the JSON Outline window highlighting the Add New Resource option.":::
 
@@ -92,40 +92,6 @@ You can customize a deployment project by modifying the Resource Manager templat
    }
    ```
 
-1. Navigate to the **HostingPlan** resource, and add a value for the **properties** with some properties.
-
-   ```json
-   "properties": {
-     "name": "[parameters('hostingPlanName')]",
-     "numberOfWorkers": 1
-   }
-   ```
-
-  You also need to define the `hostingPlanName` parameter:
-
-   ```json
-   "hostingPlanName": {
-     "type": "string",
-     "metadata": {
-       "description": "Hosting paln name."
-     }
-   }
-   ```
-
-1. Open the **WebSite.parameters.json** file. You use the parameters file to pass in values during deployment that customize the resource being deployed. Give the hosting plan a name, and save the file.
-
-   ```json
-   {
-     "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
-     "contentVersion": "1.0.0.0",
-     "parameters": {
-       "hostingPlanName": {
-         "value": "demoHostPlan"
-       }
-     }
-   }
-   ```
-
 ## Deploy project to Azure
 
 You're now ready to deploy your project to a resource group.
@@ -182,7 +148,7 @@ At this point, you've deployed the infrastructure for your app, but there's no a
 
 1. Add an **ASP.NET Core Web Application**.
 
-    :::image type="content" source="./media/create-visual-studio-deployment-project/add-app.png" alt-text="Screenshot of the New Project window with ASP.NET Core Web Application selected.":::
+    :::image type="content" source="./media/create-visual-studio-deployment-project/arm-vs-create-aspnet-core-web-app.png" alt-text="Screenshot of the New Project window with ASP.NET Core Web Application selected.":::
 
 1. Give your web app a name, and select **Create**.
 
@@ -218,18 +184,19 @@ At this point, you've deployed the infrastructure for your app, but there's no a
 
    Save your template.
 
-1. There are some new parameters in your template. They were added in the previous step. You don't need to provide values for **_artifactsLocation** or **_artifactsLocationSasToken** because those values are automatically generated. However, you have to set the folder and file name to the path that contains the deployment package. The names of these parameters end with **PackageFolder** and **PackageFileName**. The first part of the name is the name of the Web Deploy resource you added. In this article, they're named **ExampleAppPackageFolder** and **ExampleAppPackageFileName**.
+1. There are some new parameters added in the previous step. 
+
+    :::image type="content" source="./media/create-visual-studio-deployment-project/new-parameters.png" alt-text="Screenshot of the new parameters.":::
 
+   You don't need to provide values for **_artifactsLocation** or **_artifactsLocationSasToken** because those values are automatically generated. However, you have to set the folder and file name to the path that contains the deployment package. The names of these parameters end with **PackageFolder** and **PackageFileName**. The first part of the name is the name of the Web Deploy resource you added. In this article, they're named **ExampleAppPackageFolder** and **ExampleAppPackageFileName**.
+    
    Open **Website.parameters.json** and set those parameters to the values you saw in the reference properties. Set **ExampleAppPackageFolder** to the name of the folder. Set **ExampleAppPackageFileName** to the name of the zip file.
 
    ```json
    {
      "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
      "contentVersion": "1.0.0.0",
      "parameters": {
-       "hostingPlanName": {
-         "value": "demoHostPlan"
-       },
        "ExampleAppPackageFolder": {
          "value": "ExampleApp"
        },