Merge branch 'main' into copilot-agent

Author: anandmeg

.github/workflows/whats-new.yml

@@ -1590,6 +1590,26 @@
       "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/data-tools/walkthrough-creating-a-wcf-data-service-with-wpf-and-entity-framework",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/ide/reference/signing-page-project-designer.md",
+      "redirect_url": "/visualstudio/ide/how-to-sign-application-and-deployment-manifests",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/advanced-security-settings-dialog-box.md",
+      "redirect_url": "/visualstudio/deployment/how-to-enable-clickonce-security-settings",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/publish-page-project-designer.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/prerequisites-dialog-box.md",
+      "redirect_url": "/visualstudio/deployment/how-to-install-prerequisites-with-a-clickonce-application",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/deployment/how-to-enable-autostart-for-cd-installations.md",
       "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
@@ -8108,6 +8128,46 @@
       "redirect_url": "/visualstudio/get-started/csharp/tutorial-windows-forms-math-quiz-customize-ui",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/ide/reference/code-analysis-project-designer.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/code-analysis-project-designer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/property-pages-javascript.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/property-pages-javascript",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/file-properties-javascript.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/file-properties-javascript",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/options-text-editor-javascript-formatting.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/options-text-editor-javascript-formatting",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/options-text-editor-javascript-code-validation.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/options-text-editor-javascript-code-validation",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/options-text-editor-javascript-intellisense.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/options-text-editor-javascript-intellisense",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/options-text-editor-javascript-project.md",
+      "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/options-text-editor-javascript-project",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/options-text-editor-javascript-linting.md",
+      "redirect_url": "/visualstudio/javascript/linting-javascript",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/ide/quickstart-nodejs.md",
       "redirect_url": "/visualstudio/javascript/tutorial-nodejs",

.openpublishing.redirection.json

@@ -19,6 +19,16 @@
             "source_path": "subscriptions/microsoft-dev-box.md",
             "redirect_url": "/visualstudio/subscriptions",
             "redirect_document_id": false
+        },
+        {   
+            "source_path": "subscriptions/vs-whitesource.md",
+            "redirect_url": "/visualstudio/subscriptions",
+            "redirect_document_id": false
+        },
+        {
+           "source_path": "subscriptions/handle-expired-license.md",
+            "redirect_url": "/visualstudio/subscriptions",
+            "redirect_document_id": false 
         }
     ]
 }

.openpublishing.redirection.subscriptions.json

@@ -98,11 +98,11 @@ These steps are appropriate if you have more than one project that uses Docker c
 
    If you choose to create a new one, you see this screen. Provide the resource group, SKU, and choose the same region, if possible, as before. For information about the SKUs for Azure Container Registry, see [Azure Container Registry service tiers](/azure/container-registry/container-registry-skus).
 
-   ![Screenshot showing a new Azure container registry that was just created.](./media/azure-deployment-using-github-actions/github-actions-create-azure-container-registry.png)
+   ![Screenshot showing a new Azure Container Registry that was just created.](./media/azure-deployment-using-github-actions/github-actions-create-azure-container-registry.png)
 
    Once created, the new registry shows on the screen.
 
-   ![Screenshot showing creating a new Azure container registry.](./media/azure-deployment-using-github-actions/github-actions-created-azure-container-registry.png)
+   ![Screenshot showing creating a new Azure Container Registry.](./media/azure-deployment-using-github-actions/github-actions-created-azure-container-registry.png)
 
 1. The deployable projects in your solution are displayed; choose the projects you want to deploy together in the same Azure Container Apps instance.
 
@@ -140,7 +140,7 @@ WebApi_buildImageAndDeploy:
       registry: ${{ env.CONTAINER_REGISTRY_LOGIN_SERVER }}
       username: ${{ secrets.registry20230810121555_USERNAME_6891 }}
       password: ${{ secrets.registry20230810121555_PASSWORD_6891 }}
-  - name: Build and push Docker image to Azure container registry
+  - name: Build and push Docker image to Azure Container Registry
     uses: docker/build-push-action@v4
     with:
       push: true
@@ -173,7 +173,7 @@ WebFrontEnd_buildImageAndDeploy:
       registry: ${{ env.CONTAINER_REGISTRY_LOGIN_SERVER }}
       username: ${{ secrets.registry20230810121555_USERNAME_2047 }}
       password: ${{ secrets.registry20230810121555_PASSWORD_2047 }}
-  - name: Build and push Docker image to Azure container registry
+  - name: Build and push Docker image to Azure Container Registry
     uses: docker/build-push-action@v4
     with:
       push: true
@@ -210,7 +210,7 @@ DOCKER_FILEPATH_WEBFRONTEND: docker/ComposeSample/WebFrontend/Dockerfile
 Use the values of these environment variables for the `file` parameter as follows:
 
   ```yml
-  - name: Build and push Docker image to Azure container registry
+  - name: Build and push Docker image to Azure Container Registry
     uses: docker/build-push-action@v4
     with:
       push: true

docs/azure/azure-deployment-using-github-actions.md

@@ -24,6 +24,9 @@ If you've already installed Visual Studio:
 - Install the latest updates in Visual Studio by selecting **Help** > **Check for Updates**.
 - Verify the **ASP.NET and web development** and **Azure development** workloads are installed by selecting **Tools** > **Get Tools and Features**.
 
+> [!WARNING]
+> This article makes use of connection strings. Use caution when managing connections using usernames, passwords, or access keys. These secrets shouldn't be committed to source control or placed in unsecure locations where they might be accessed by unintended users. During local development, you'll generally connect to a local database that doesn't require storing secrets or connecting directly to Azure. During production, [connect to your Azure SQL database using a secretless approach](/azure/azure-sql/database/azure-sql-dotnet-entity-framework-core-quickstart) such as [Microsoft Entra ID](/entra/fundamentals/whatis) when possible.
+
 ## Set up the sample app locally
 
 Use the TODO sample app to follow along with this tutorial. Clone the app from GitHub using the following command:
@@ -115,7 +118,7 @@ The publishing features of Visual Studio can handle creating these resources for
         - Select **Ok** to close the container apps environment dialog.
     - Select **Create** to close the original container apps dialog. Visual Studio creates the container app resource in Azure.
 1. Once the resource is created, make sure it's selected in the list of container apps, and then select **Next**.
-1. You'll need to create an Azure container registry to store the published image artifact for your app. Select the green **+** icon on the **Container Registry** screen.
+1. You'll need to create an Azure Container Registry to store the published image artifact for your app. Select the green **+** icon on the **Container Registry** screen.
 
     :::image type="content" source="./media/end-to-end-deployment-entity-framework-core-github-actions/visual-studio-container-registry.png" lightbox="./media/end-to-end-deployment-entity-framework-core-github-actions/visual-studio-container-registry-large.png" alt-text="A screenshot showing how to create a new container registry.":::
 

docs/azure/end-to-end-deployment-entity-framework-core-github-actions.md

@@ -1,7 +1,7 @@
 ---
 title: Migrate from FxCop to source analysis (.NET)
 description: Analyze code for the first time or migrate your process from binary analysis (FxCop code analysis) to .NET analyzers for source analysis.
-ms.date: 09/17/2021
+ms.date: 04/30/2025
 ms.topic: conceptual
 f1_keywords:
  - "vs.projectpropertypages.codeanalysis"
@@ -50,6 +50,8 @@ To learn more about how to configure the .NET analyzers:
 
 - To find out about configuring analyzers using predefined rules with EditorConfig or a rule set file, see [Enable a category of rules](/dotnet/fundamentals/code-analysis/code-quality-rule-options).
 
+- To migrate from rule set files to EditorConfig, see [Convert an existing rule set file to an EditorConfig file](../code-quality/use-roslyn-analyzers.md#convert-an-existing-rule-set-file-to-an-editorconfig-file).
+
 ## Related content
 
 - [Migrate from FxCop analyzers to .NET analyzers](migrate-from-fxcop-analyzers-to-net-analyzers.md)

docs/code-quality/migrate-from-legacy-analysis-to-net-analyzers.md

@@ -24,7 +24,7 @@ Analyzers are divided into the following groups:
 
 - [Code style analyzers](/dotnet/fundamentals/code-analysis/code-style-rule-options?preserve-view=true&view=vs-2019#convention-categories)
 
-   These analyzers are built into Visual Studio. The analyzer's diagnostic ID, or code format is IDExxxx, for example, IDE0001. You can configure preferences in the [text editor options page](../ide/code-styles-and-code-cleanup.md#code-styles-in-the-options-dialog-box) or in an [EditorConfig file](../ide/create-portable-custom-editor-options.md). Starting in .NET 5.0, code style analyzers are included with the .NET SDK and can be strictly enforced as build warnings or errors. For more information, see [Overview of .NET source code analysis](/dotnet/fundamentals/productivity/code-analysis).
+   These analyzers are built into Visual Studio. The analyzer's diagnostic ID, or code format is IDExxxx, for example, IDE0001. You can configure preferences in the [text editor options page](../ide/code-styles-and-code-cleanup.md#net-code-styles-in-the-options-dialog-box) or in an [EditorConfig file](../ide/create-portable-custom-editor-options.md). Starting in .NET 5.0, code style analyzers are included with the .NET SDK and can be strictly enforced as build warnings or errors. For more information, see [Overview of .NET source code analysis](/dotnet/fundamentals/productivity/code-analysis).
 
 - [Code quality analyzers](/dotnet/fundamentals/code-analysis/overview#code-quality-analysis)
 

docs/code-quality/roslyn-analyzers-overview.md

@@ -10,7 +10,7 @@ helpviewer_keywords:
 - code analysis, managed code
 - analyzers
 - Roslyn analyzers
-ms.date: 04/04/2024
+ms.date: 04/30/2025
 ---
 
 # Customize Roslyn analyzer rules
@@ -265,7 +265,7 @@ When you convert your existing rule set file to an EditorConfig file, save it at
 You can convert an existing rule set file to an EditorConfig file by using either the rule set editor or the command line.
 
 > [!NOTE]
-> .NET Core and .NET Standard projects don't support the menu commands for rule sets in Solution Explorer, for example, **Open Active Rule Set**. To specify a non-default rule set for a .NET Core or .NET Standard project, manually [add the **CodeAnalysisRuleSet** property](using-rule-sets-to-group-code-analysis-rules.md#specify-a-rule-set-for-a-project) to the project file. You can still configure the rules within the rule set in the rule set editor.
+> .NET Core and .NET 5+ projects don't support the menu commands for rule sets in Solution Explorer, for example, **Open Active Rule Set**. To specify a non-default rule set for a .NET Core or a .NET 5+ project, manually [add the **CodeAnalysisRuleSet** property](using-rule-sets-to-group-code-analysis-rules.md#specify-a-rule-set-for-a-project) to the project file. You can still configure the rules within the rule set in the rule set editor.
 
 To use the rule set editor, follow these steps. If your project already uses a specific rule set file for its `CodeAnalysisRuleSet` property value, you can convert it to an equivalent EditorConfig file from the rule set editor:
 
@@ -281,6 +281,11 @@ To use the rule set editor, follow these steps. If your project already uses a s
 
    The generated EditorConfig opens in the editor. Additionally, the MSBuild property `CodeAnalysisRuleSet` is updated in the project file so that it no longer references the original rule set file.
 
+   The original rule set file can be removed from the project.
+
+   > [!NOTE]
+   > In a .NET Framework project, the default rule set file can't be migrated or removed from the project.
+
 To use the command line, follow these steps:
 
 1. Install the NuGet package [Microsoft.CodeAnalysis.RulesetToEditorconfigConverter](https://www.nuget.org/packages/Microsoft.CodeAnalysis.RulesetToEditorconfigConverter).